From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: rfh: mingw guile.exe stalled by impact of 28dc10a4
Date: Sat, 11 Jun 2016 11:02:30 +0200 [thread overview]
Message-ID: <87d1no6qu1.fsf@gnu.org> (raw)
In-Reply-To: <874m974c2n.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Sun, 05 Jun 2016 22:26:08 +0200")
Jan Nieuwenhuizen writes:
Hi!
Some more info, still no full picture.
TL;DR: 28dc10a4 breaks the cross build on master (i.e. reverting it
fixes the cross build), but core-updates has 28dc10a4 and there the
cross build works. So cross building with 28dc10a4 depends on something
else that is in core-updates which is missing from master.
Progress at
https://gitlab.com/janneke/guix
branches v9 and v9-core.
My v9 mingw patch set rebased on current master cannot cross build
readline
./pre-inst-env guix build --target=i686-w64-mingw32 readline
...
@ build-failed /gnu/store/m6gq2xz5kd3vn4zm1i0i6j0immlgyhmg-make-boot0-4.1.drv - 1 builder for `/gnu/store/m6gq2xz5kd3vn4zm1i0i6j0immlgyhmg-make-boot0-4.1.drv' failed with exit code 1
cannot build derivation `/gnu/store/1fjnm2x2az4z4qaz3bad5p5zbygf5wqs-gcc-cross-boot0-4.9.3.drv': 1 dependencies couldn't be built
guix build: error: build failed: build of `/gnu/store/1fjnm2x2az4z4qaz3bad5p5zbygf5wqs-gcc-cross-boot0-4.9.3.drv' failed
Should that make-boot0 cross-build cross succeed...
./pre-inst-env guix build --target=x86_64-linux-gnu make-boot0
guix build: error: make-boot0: unknown package
hmm, how to find out?...or should in not happen and in that case, what
erroneously makes it happen?
Reverting commit
commit 28dc10a455689c807abc9241ed1094d902a9d9fa
Author: Ludovic Courtès <ludo@gnu.org>
Date: Sun May 29 23:15:14 2016 +0200
gnu: glibc: Refer to the target kernel headers when cross-compiling.
makes the make-boot0 error go away, readline and guile.exe cross build.
I don't know how to find out if the make-boot0 build succeeded, or did
not happen?
However I have rebased onto core-updates, which also has commit 28dc10a4,
and there readline and guile.exe cross build succeed.
So, last week I spent cherry-picking patches from core-updates onto
master in an effort to investigate what's going on.
Sofar I have tried
fb341ca gnu: commencement: Disable Texinfo tests during bootstrap.
461513b profiles: 'profile-derivation' now honors #:system.
0f24c8d gnu: perl: Do not retain references to GCC & co.
and have run almost out of inspiration what to try looking at the diff
between v9 and v9-core, I have now added
9e574f6 gnu: glibc: Update to 2.23.
and am looking at another Guile build...we'll see.
Greetings,
Jan
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
prev parent reply other threads:[~2016-06-11 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 12:05 rfh: mingw guile.exe stalled by impact of 28dc10a4 Jan Nieuwenhuizen
2016-06-05 20:13 ` Ludovic Courtès
2016-06-05 20:26 ` Jan Nieuwenhuizen
2016-06-11 9:02 ` Jan Nieuwenhuizen [this message]
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=87d1no6qu1.fsf@gnu.org \
--to=janneke@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 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).