From: "Ludovic Courtès" <ludo@gnu.org>
To: zamfofex <zamfofex@twdb.moe>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: GMP GCC C++ Hurd cross-build failure on core-updates
Date: Mon, 05 Dec 2022 17:08:25 +0100 [thread overview]
Message-ID: <87fsdtq1dy.fsf@gnu.org> (raw)
In-Reply-To: <1309771808.1564506.1670138591125@privateemail.com> (zamfofex@twdb.moe's message of "Sun, 4 Dec 2022 04:23:11 -0300 (BRT)")
Hello!
zamfofex <zamfofex@twdb.moe> skribis:
> Updating Mig required a more recent glibc than what was available in Guix at the time, so I worked on <https://issues.guix.gnu.org/54832> to update glibc.
Nice!
> Now that the recent glibc is on core-updates, I picked up my work once again. I updated the packages to the latest commits, and updated Mig! However, I ran into an issue while trying to build a system image. The issue is that GMP fails to cross‐compile during the ‘configure’ phase becase the cross‐compiling ‘g++’ is not functional.
Could you paste the command you used and the tail of the build log?
I tried this:
guix time-machine --branch=core-updates -- build --target=i586-pc-gnu gmp
… but there are too many missing substitutes at this point. :-)
> +++ b/gnu/system.scm
> @@ -771,9 +771,7 @@ (define (hurd-default-essential-services os)
> %boot-service
> %hurd-startup-service
> %activation-service
> - (service shepherd-root-service-type
> - (shepherd-configuration
> - (shepherd shepherd-0.8))) ;no Fibers
> + (service shepherd-root-service-type)
We still need ‘shepherd-0.8’ here.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-12-05 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 7:23 GMP GCC C++ Hurd cross-build failure on core-updates zamfofex
2022-12-04 16:46 ` Joshua Branson
2022-12-05 16:08 ` Ludovic Courtès [this message]
2022-12-06 10:06 ` zamfofex
2022-12-06 11:20 ` zamfofex
2022-12-08 15:43 ` Ludovic Courtès
2022-12-19 21:06 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2022-12-15 7:24 Nathan Dehnel
2022-12-15 11:17 ` Svante Signell
2022-12-19 10:57 ` Svante Signell
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=87fsdtq1dy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=zamfofex@twdb.moe \
/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.