Re: [PATCH] gnu: cross-gcc-arguments: Disable libitm, libvtv and, libsanitizer.

[Ricardo Wurmus <rekado@elephly.net>]

宋文武 <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