Re: [Patches] GCC_NO_EXECUTABLES

[Christer Solskogen <christer.solskogen@xxxxxxxxx>]

On Thu, Dec 8, 2011 at 6:51 PM, Joseph S. Myers <joseph@xxxxxxxxxxxxxxxx> wrote:
> On Thu, 8 Dec 2011, Christer Solskogen wrote:
>
>> I tried following the EGLIBC.cross-building (also with Steve
>> Longerbeam patch from November) but I cant get the first GCC to build.
>> It fails with configure: error: Link tests are not allowed after
>> GCC_NO_EXECUTABLES.
>
> That's not sufficient information. ÂYou need to identify what directory
> was being configured that gave that message.
>

Oh, sorry. Maybe this will help:
checking whether the
/home/solskogen/obj/gcc-cross_tools_stage1/./gcc/xgcc
-B/home/solskogen/obj/gcc-cross_tools_stage1/./gcc/
-B/opt/cross/powerpc-centix-linux/bin/
-B/opt/cross/powerpc-centix-linux/lib/ -isystem
/opt/cross/powerpc-centix-linux/include -isystem
/opt/cross/powerpc-centix-linux/sys-include    linker
(/home/solskogen/obj/gcc-cross_tools_stage1/./gcc/collect-ld) supports
shared libraries... yes
checking dynamic linker characteristics... configure: error: Link
tests are not allowed after GCC_NO_EXECUTABLES.
make[1]: *** [configure-target-zlib] Error 1
make[1]: Leaving directory `/home/solskogen/obj/gcc-cross_tools_stage1

> The real problem is rarely that error you quoted. ÂIt's normally either a
> directory being configured that shouldn't have been, or an earlier link
> test failing that should have passed; it's rare for the problem to be with
> the actual link test giving that error (i.e. for the logic in configure to
> be running that test in a case when it should have known to disable it).
>

I see. Thanks for pointing out. I'll try with disabled zlib this time.

-- 
chs,
_______________________________________________
Patches mailing list
Patches@xxxxxxxxxx
http://eglibc.org/cgi-bin/mailman/listinfo/patches