Build failure in eglibc, locale related
Bryan Hundven
bryanhundven@gmail.com
Tue May 8 01:39:00 GMT 2012
On Sun, May 6, 2012 at 6:21 AM, Benoît Thébaudeau
<benoit.thebaudeau@advansee.com> wrote:
Hi Yann, Benoît, Thomas, all,
>
>> Final gcc-4.7 still breaks (Link tests are not allowed after
>> GCC_NO_EXECUTABLES).
>
> FYI, same for me with Linaro GCC 4.7-2012.04.
>
> Regards,
> Benoît
I'm seeing the same problem Yann explained:
----------------------------------------------------------------------
[ALL ] checking whether the
/work/tc-work/cortex-a8/.build/arm-unknown-linux-gnueabi/build/build-cc-final/./gcc/xgcc
-B/work/tc-work/cortex-a8/.build/arm-unknown-linux-gnueabi/build/build-cc-final/./gcc/
-B/home/bryan/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/bin/
-B/home/bryan/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/lib/
-isystem /home/bryan/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/include
-isystem /home/bryan/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sys-include
linker (/work/tc-work/cortex-a8/.build/arm-unknown-linux-gnueabi/build/build-cc-final/./gcc/collect-ld)
supports shared libraries... yes
[ERROR] checking whether -lc should be explicitly linked in...
make[3]: *** [configure-target-libstdc++-v3] Error 1
[ALL ] make[3]: *** Waiting for unfinished jobs....
[ALL ] no
[ERROR] checking dynamic linker characteristics... configure:
error: Link tests are not allowed after GCC_NO_EXECUTABLES.
[ERROR] make[3]: *** [configure-target-libquadmath] Error 1
[ALL ] make[3]: Leaving directory
`/work/tc-work/cortex-a8/.build/arm-unknown-linux-gnueabi/build/build-cc-final'
[ERROR] make[2]: *** [all] Error 2
[ALL ] make[2]: Leaving directory
`/work/tc-work/cortex-a8/.build/arm-unknown-linux-gnueabi/build/build-cc-final'
----------------------------------------------------------------------
However my locales built fine. It would still be interesting to see
your full build.log, Thomas.
-Bryan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
More information about the crossgcc
mailing list