[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23376: Bootstrap failure on'binutils-cross-boot0-2.25.1: cannot find
bug#23376: Bootstrap failure on'binutils-cross-boot0-2.25.1: cannot find -lstdc++
Wed, 04 May 2016 10:07:54 +0200
mu4e 0.9.17; emacs 22.214.171.124
Description: Text document
Description: Text Data
Ludovic Courtès writes:
> Roel Janssen <address@hidden> skribis:
>> In an attempt to bootstrap Guix, I repeatedly encounter the same error.
>> I attached the last 5000 lines of the build output of the command:
>> guix build bootstrap-tarballs
>> When running the daemon, I used the following environment variables:
> And TMPDIR?
I didn't set TMPDIR. Should I do that?
> (For recent versions of guix-daemon, TMPDIR has no effect on the build
> chroot. I assume this uses a recent guix-daemon.)
Checkout out and compiled at the day I submitted the bug report.
> Note that these environment variables are undocumented; use at your own
> risks. :-)
Ha! I found them in the code for the guix-daemon. Unrelated to this
bugreport, but don't you think we should rename these to GUIX_*
equivalent environment variables?
>> The same environment variables (and values) were set when running the
>> guix build command.
>> What am I doing that causes the build to fail?
> Did you pass the --disable-chroot or --chroot-directory options of
No, but I have made some modifications to the code to make it run
completely in userspace. The code should effectively disable chrooting
I attached a patch displaying the differences between the version I used
and commit 85f0945.
> The log you sent suggests a failure to build (@@ (gnu packages
> commencement) gcc-final) because the directory is called “gcc-4.9.3”,
> not “gcc-cross-boot0-4.9.3”. However, it also shows that
> binutils-cross-boot0 is used, which is not the case for ‘gcc-final’.
> What Guix commit are you using?
I'm using commit 85f09459162d12e7ce7874995ae2837164ed17ee (with the
modifications in my patch).
> Could you identify more precisely what’s failing to build? For
> instance, you can run:
> guix build -e '(@@ (gnu packages commencement) gcc-boot0)'
> guix build -e '(@@ (gnu packages commencement) gcc-final)'
It seems the problem arises when building gcc-final. I attached the
complete output of both commands. Because the output for gcc-final is
rather large, I compressed it.
Thanks for your time!