From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: cross-gcc-arguments: Disable libitm, libvtv and, libsanitizer.
Date: Mon, 04 Jul 2016 10:25:00 +0200 [thread overview]
Message-ID: <8737nphktf.fsf@gnu.org> (raw)
In-Reply-To: <20160624083231.GA7766@debian-netbook> (Efraim Flashner's message of "Fri, 24 Jun 2016 11:32:31 +0300")
Hi,
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, Apr 07, 2016 at 04:07:25PM +0300, Manolis Ragkousis wrote:
>> Hey Ludo,
>>
>> I have reproduced the problem on the latest master targeting i686-linux
>> and arm-linux-gnueabihf.
>>
>> The problem is that those libraries will fail to build when glibc is not
>> present. Also if target os is none, this problem will not appear because
>> the libs will not get built at all.
>>
>> You can reproduce it with ./pre-inst-env guix build -e '((@@(gnu
>> packages cross-base) cross-gcc) "arm-linux-gnueabihf")'
>>
>> This does not happen when targeting mips.
>>
>> I have added an explanation to the patch and a link to this thread.
>>
>> Manolis
>
> This patch was instrumental in building aarch64 bootstrap tarballs.
> Without it, when building the cross-gcc compiler from x86_64 to aarch64
> it would fail to compile when trying to build libitm. Searching around
> the internet suggested that this was only when building a cross-compiler
> that targeted C++ and not only C.
>
> I understand that it's too late to push this to core-updates, but we
> should push it to core-updates-next.
Sorry for the delay again. Since it touches the cross toolchain and not
the main toolchain (Manolis, could you double-check that this is
correct, by making sure that “./pre-inst-env guix build coreutils -d” is
the same both before and after the patch?), it’s still OK to push to
‘core-updates’.
Manolis: OK to push?
Thanks for the heads-up, Efraim!
Ludo’.
prev parent reply other threads:[~2016-07-04 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 13:23 [PATCH] gnu: cross-gcc-arguments: Disable libitm, libvtv and, libsanitizer Manolis Ragkousis
2016-02-23 12:20 ` Manolis Ragkousis
2016-02-23 13:14 ` Ricardo Wurmus
2016-02-28 14:23 ` 宋文武
2016-02-28 14:43 ` Ricardo Wurmus
2016-03-04 14:09 ` Manolis Ragkousis
2016-03-13 22:23 ` Ludovic Courtès
2016-04-07 13:07 ` Manolis Ragkousis
2016-06-24 8:32 ` Efraim Flashner
2016-07-04 8:25 ` Ludovic Courtès [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=8737nphktf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--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).