From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, 40006@debbugs.gnu.org
Subject: Re: `guix build hello' now succeeds on the Hurd
Date: Tue, 10 Mar 2020 09:59:02 +0100 [thread overview]
Message-ID: <87a74o4mcp.fsf@gnu.org> (raw)
In-Reply-To: <87imjdzc76.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 09 Mar 2020 18:10:21 +0100")
Ludovic Courtès writes:
>> 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.)
I have slightly cleaned-up a patch by Manolis so that I can run
sudo ./pre-inst-env guix-daemon --disable-chroot --build-users-group=guixbuild &
This and other useful recipes I have noted in my scratchbook on the Hurd
https://gitlab.com/janneke/guix/-/blob/wip-hurd-system/THE-HURD
I briefly looked at more work-in-progress daemon patches by Manolis, but
stopped when I found that it needs [t]his "new" libhurdutils library...
@Manolis?
> 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.
Great, thanks, done; follow-up here!
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40006
https://issues.guix.info/issue/40006
>> 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!)!
Yes, that would be awesome!
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-10 8:59 UTC|newest]
Thread overview: 9+ 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
2020-03-09 18:11 ` Ricardo Wurmus
2020-03-10 9:26 ` Jan Nieuwenhuizen
2020-03-10 8:59 ` bug#40006: " Jan Nieuwenhuizen
2020-03-10 8:59 ` Jan Nieuwenhuizen [this message]
2020-03-10 15:04 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a74o4mcp.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=40006@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.