From: Svante Signell <svante.signell@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Hurd bootstrap breaks guix building binutils-boot0@2.34
Date: Sat, 29 Feb 2020 12:20:30 +0100 [thread overview]
Message-ID: <a332cea1a5f15ede59b794f1eb10e59dd87514ef.camel@gmail.com> (raw)
In-Reply-To: <877e05ka5s.fsf@gnu.org>
Hello,
I did build the bootstrap binaries some time ago. They were corrupt. As well as
the pre-built ones that were available at
http://berlin.guix.gnu.org/guix/bootstrap/i586-gnu/20190508
Down-grading from guile-2.2 to guile-2.0 did not improve the situation.
Now I have a project to cross-build Hurd from a GNU/Linux box: hurd-cross, using
the latest versions of the gnumach, hurd, glibc, gcc, etc. The built Hurd boots
and runs fine in a VM :) The project will soon be available on Savannah. From
there I will again cross-build the bootstrap binaries for Hurd, in due time
though. (Other packages, like ones not yet available natively, can also be
cross-built. That's an interesting extension.)
See
https://lists.gnu.org/archive/html/guix-devel/2019-08/msg00198.html
https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00000.html
https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00014.html
https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00225.html
for some of the efforts to make Guix work on GNU/Hurd.
Thanks!
(and sorry for top-posting)
On Sat, 2020-02-29 at 10:36 +0100, Jan Nieuwenhuizen wrote:
> Hi!
>
> I have been looking at the recent work of Efraim and others wrt the Hurd
> bootstrap. On the Hurd, make-boot0 v4.3 did not work for me so I
> reverted to make-boot0 v4.1 for now. Now I'm stuck on building
> binutils-boot0
>
> ./pre-inst-env guix build -e '(@@ (gnu packages commencement) binutils-
> boot0)'
>
> It almost fully builds but fails with this error
>
> phase `compress-documentation' succeeded after 0.4 seconds
> error: cannot kill processes for uid `999': Operation not permitted
> guix build: error: cannot kill processes for uid `999': failed with exit
> code 1
>
> after which my Hurd setup is broken; I haven't been able to build a new
> package and had to reinstall my Hurd VM. This error is reproducible for
> me however: I tried again and broke my Hurd setup in exact the same way.
> Any ideas what may be going wrong and how to fix this?
>
> I am now looking to revert bootstrap-guile to v2.0
> (https://lists.gnu.org/archive/html/guix-devel/2019-09/msg00106.html)
> and possibly binutils-boot0 to v2.32.
>
> Find my notes attached for how I am setting up Hurd development for Guix.
>
> Greetings,
> janneke
>
next prev parent reply other threads:[~2020-02-29 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 9:36 Hurd bootstrap breaks guix building binutils-boot0@2.34 Jan Nieuwenhuizen
2020-02-29 11:20 ` Svante Signell [this message]
2020-02-29 17:18 ` Jan Nieuwenhuizen
-- strict thread matches above, loose matches on Subject: below --
2020-02-29 14:26 Rene
2020-02-29 15:45 ` 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
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=a332cea1a5f15ede59b794f1eb10e59dd87514ef.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 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).