From: Ricardo Wurmus <rekado@elephly.net>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: cross-gcc-arguments: Disable libitm, libvtv and, libsanitizer.
Date: Sun, 28 Feb 2016 15:43:52 +0100 [thread overview]
Message-ID: <87r3fwdhef.fsf@elephly.net> (raw)
In-Reply-To: <87oab0ncc8.fsf@member.fsf.org>
宋文武 <iyzsong@member.fsf.org> writes:
> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>
>> Manolis Ragkousis <manolis837@gmail.com> writes:
>>
>>> This is a follow up to better explain what the problem is with the
>>> sans-libc cross gcc in the (gnu packages cross-base) module.
>>>
>>> In the latest master if you try to build gcc-cross-sans-libc with:
>>>
>>> ./pre-inst-env guix build -e '((@@(gnu packages cross-base) cross-gcc)
>>> "i686-linux-gnu")' -c8
>>>
>>> gcc modules libitm, libvtv and libsanitizer fail to build with
>>> "configure: error: C compiler cannot create executables".
>>>
>>> This happens because there is no libc present at that point and the
>>> problem was introduced with commit ca7ef4d41854218c which enabled c++.
>>
>> I find this very odd. I’m the author of that commit and I did this to
>> be able to build a C and C++ cross compiler for arm-none-eabi (which I
>> still haven’t submitted to the ML). At no point did I see any errors
>> about libitm, libvtv, or libsanitizer.
>>
> On the master, ‘arm-linux-gnueabihf’ also failed.
> Look at the end of ‘configure.tgt’ scripts of libitm, libvtv and
> libsanitizer, the target is matched with some well-known OS (eg: linux,
> gnu, etc.). So, I think those libraries won’t build at all when you’re
> using ‘none’ as OS.
Ah, this makes sense. Thanks for the clarification.
~~ Ricardo
next prev parent reply other threads:[~2016-02-28 14:44 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 [this message]
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
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=87r3fwdhef.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.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 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.