From: Svante Signell <svante.signell@gmail.com>
To: guix-devel@gnu.org
Subject: Re: `guix build hello' now succeeds on the Hurd
Date: Fri, 06 Mar 2020 11:41:41 +0100 [thread overview]
Message-ID: <7ec2c020e26991c1d67cd0a74c2873b91697879b.camel@gmail.com> (raw)
In-Reply-To: <878skd94d4.fsf@gnu.org>
Congratulations!!
On Fri, 2020-03-06 at 11:15 +0100, Jan Nieuwenhuizen wrote:
> Hi Guix!
>
> 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/
>
> Current development lives on the `wip-hurd-bootstrap' branch @ my
> personal gitlab
>
> https://gitlab.com/janneke/guix #wip-hurd-bootstrap
>
> 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).
>
> Most controversial/problematic is the need to use fairly recent gnumach
> and hurd sources. Somehow the bootstrap in commencement currently tries
> to usee GIT versions of those (gnumach-headers-boot0,
> hurd-headers-boot0), creating a bootstrap dependency loop. I tried
> building from release tarballs with patches but in the end I "simply"
> ran `make dist' for gnumach and hurd and use those source tarballs.
>
> I have built bootstrap tarballs
>
> ./pre-inst-env guix build --target=i586-pc-gnu bootstrap-tarballs
>
> and put them up at
>
> http://lilypond.org/janneke/guix/i586-gnu/20200304/
>
> Gnumach and Hurd tarball sources are here
>
> http://lilypond.org/janneke/hurd
>
> I have included my setup/install instructions in Git
>
> https://gitlab.com/janneke/guix/-/blob/wip-hurd-bootstrap/THE-HURD
>
> What could be the next step? We have a stale branch `wip-hurd' at
> savannah by Manolis and Efraim's recent wip-hurd-bootstrap (which I
> started from, but rewrote).
>
> Shall I push this to savannah as `wip-hurd' (possibly save wip-hurd->
> `wip-hurd-old?); I could also rewrite wip-hurd-bootstrap?
>
> When we mave a branch I'd like to open a bug report on merging it,
> and setting up build hosts (as discussed with Ricardo on IRC).
>
> Greetings,
> janneke
>
next prev parent reply other threads:[~2020-03-06 10:40 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 [this message]
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 ` Jan Nieuwenhuizen
2020-03-10 15:04 ` bug#40006: " Manolis Ragkousis
2020-03-10 8:59 ` Jan Nieuwenhuizen
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=7ec2c020e26991c1d67cd0a74c2873b91697879b.camel@gmail.com \
--to=svante.signell@gmail.com \
--cc=guix-devel@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.