From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Ricardo Wurmus <rekado@elephly.net>, 28433@debbugs.gnu.org
Subject: [bug#28433] [WIP] Rust update
Date: Mon, 30 Oct 2017 17:14:15 +0100 [thread overview]
Message-ID: <20171030171415.0cf6c27d@scratchpost.org> (raw)
In-Reply-To: <8760aw7ijp.fsf@gnu.org>
Hi Ludo,
> Yes, I think -m32 is a no-op in this case.
Yep. I just got rustc to build a bootstrap executable (which fails when executing it [*], but hey, progress) by making a union-build with all the i686 libs.
Feels kinda icky, but it seems that propagated-inputs don't remember the #:system it was for, so for example if A propagates B and A specifies system i686, and X specifies system x86_64 and X depends on A, then X's B will be x86_64. Weird but understandable I guess...
Details:
A:
propagated-inputs
B
arguments system i686
X:
native-inputs
A
arguments system x86_64
Now X's B is x86_64...
The workaround is this:
A:
arguments system i686
native-inputs
B
union-build out/lib from B (etc)
X:
native-inputs
A
arguments system x86_64
That works.
In our specific case A = "rust-bootstrap", X = "rustc", B = "glibc", "gcc:lib" etc.
[*] Tries to load libgcc_s.so.1 from the glibc store directory. WTF?
next prev parent reply other threads:[~2017-10-30 16:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 16:50 [bug#28433] [WIP] Rust update Danny Milosavljevic
2017-10-25 14:19 ` Ricardo Wurmus
2017-10-26 8:17 ` Danny Milosavljevic
2017-10-28 10:42 ` Danny Milosavljevic
2017-10-28 11:31 ` Danny Milosavljevic
2017-10-28 11:57 ` Danny Milosavljevic
2017-10-28 18:26 ` Ludovic Courtès
2017-10-30 11:35 ` Danny Milosavljevic
2017-10-30 15:38 ` Ludovic Courtès
2017-10-30 16:14 ` Danny Milosavljevic [this message]
2017-11-28 6:35 ` ng0
2017-11-28 10:12 ` Danny Milosavljevic
2017-11-29 8:04 ` Danny Milosavljevic
2017-10-28 15:36 ` ng0
2017-10-28 18:32 ` Ludovic Courtès
2017-10-30 19:18 ` [bug#28433] [WIP] v2 " Danny Milosavljevic
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=20171030171415.0cf6c27d@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=28433@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/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.