From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: `guix build hello' now succeeds on the Hurd
Date: Mon, 09 Mar 2020 18:10:21 +0100 [thread overview]
Message-ID: <87imjdzc76.fsf@gnu.org> (raw)
In-Reply-To: <878skd94d4.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Fri, 06 Mar 2020 11:15:03 +0100")
Hello!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> The situation on the Hurd starts to look pretty good
>
> janneke@debian:~/src/guix$ ./pre-inst-env guix build hello --no-offload
> /gnu/store/a2sylb94rm1b6qxcp5mqvgiyx9szipz7-hello-2.10
> janneke@debian:~/src/guix$ /gnu/store/a2sylb94rm1b6qxcp5mqvgiyx9szipz7-hello-2.10/bin/hello
> Hello, world!
>
> \o/
Woohoo! Congrats!
How do you run guix-daemon? (In the future it’d be great to perhaps
implement Linux namespaces on the Hurd in libc.)
> It has some 20 odd patches. I chose to create workarounds to "get early
> success" rather than doing everything right. While I worked on forward
> porting glibc patches, I only took the minimal set that I needed. Also,
> I reverted to make 4.1 instead of debugging why make 4.3 fails (for
> now).
OK.
> Most controversial/problematic is the need to use fairly recent gnumach
> and hurd sources.
That’s OK IMO.
> What could be the next step?
Merging what you have—the earlier the better. :-)
> Shall I push this to savannah as `wip-hurd' (possibly save wip-hurd->
> `wip-hurd-old?);
Yup, sounds like a plan.
> I could also rewrite wip-hurd-bootstrap?
Dunno!
To me, the difficult bit with porting and bootstrapping work is making
sure that bootstrap.scm/commencement.scm/base.scm/cross-base.scm remain
maintainable. All this complexity adds up so we must spend time trying
to, for instance, minimize variation across platforms/OSes. Every line
of code and above all every conditional avoided in these files is a win
in the not-so-long term. That’d be my guideline as we merge it. :-)
Anyhow, thumbs up! I’m looking forward to merging it and having it
built on CI (we could offload to a Debian VM!)!
Ludo’.
next prev parent reply other threads:[~2020-03-09 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 10:15 `guix build hello' now succeeds on the Hurd Jan Nieuwenhuizen
2020-03-06 10:41 ` Svante Signell
2020-03-06 15:44 ` Tanguy Le Carrour
2020-03-09 17:10 ` Ludovic Courtès [this message]
2020-03-09 18:11 ` Ricardo Wurmus
2020-03-10 9:26 ` Jan Nieuwenhuizen
2020-03-10 8:59 ` Jan Nieuwenhuizen
2020-03-10 15:04 ` bug#40006: " Manolis Ragkousis
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=87imjdzc76.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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).