From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 40006@debbugs.gnu.org
Subject: bug#40006: [core-updates] Merge wip-hurd
Date: Thu, 26 Mar 2020 13:25:32 +0100 [thread overview]
Message-ID: <87d08zwber.fsf@gnu.org> (raw)
In-Reply-To: <87h7yw4muy.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 10 Mar 2020 09:48:05 +0100")
Jan Nieuwenhuizen writes:
> Hello Guix'y supporters of the Hurd,
`wip-hurd' is now pushed to core-updates as
3a1c3642d4d611c5516a8ba5b6bc7e39bdc1c9ae
As discussed on IRC yesterday, we did it in two stages: we first
merged all work necessary to build sensible bootstrap binaries
to core-updates:
3342a1182b15ec031f0ec6f602fd96c1dca3d4b0
then we build bootstrap binaries and verified the result, producing
this commit message
--8<---------------cut here---------------start------------->8---
On 3342a1182b15ec031f0ec6f602fd96c1dca3d4b0
gnu: make-bootstrap: Use _IOLBF on Guile 2.0 only.
Run
./pre-inst-env guix build --target=i586-pc-gnu bootstrap-tarballs --verbosity=1
Producing
/gnu/store/lhca65c997pvic5cfrpm0dasniwqlg2a-bootstrap-tarballs-0
With guix hash -rx /gnu/store/lhca65c997pvic5cfrpm0dasniwqlg2a-bootstrap-tarballs-0
07jnq2by98f2a45k8wd2gj62iazvwfa4z7p3w3id4m1g0fdsvc3b
--8<---------------cut here---------------end--------------->8---
Next up is to work towards getting a bootable guix image for the Hurd
and other porting work in the Debian VM.
See:
https://gitlab.com/janneke/guix/-/blob/wip-hurd-system/THE-HURD
but that's a whole other stage of effort, I'm tempted to close this bug
and open a new one (or two?) for that. WYDT?
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-03-26 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 8:48 bug#40006: [core-updates] Merge wip-hurd Jan Nieuwenhuizen
2020-03-10 8:54 ` Manolis Ragkousis
2020-03-26 12:25 ` Jan Nieuwenhuizen [this message]
2020-03-26 12:51 ` Efraim Flashner
2020-03-26 14:08 ` Jan Nieuwenhuizen
2020-03-26 14:26 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d08zwber.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=40006@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).