[oe] glibc_2.9 compile failed for armv5te

Khem Raj raj.khem at gmail.com
Fri Oct 16 20:54:01 UTC 2009


On Fri, Oct 16, 2009 at 7:51 AM, Steffen Sledz <sledz at dresearch.de> wrote:
> Phil Blundell wrote:
>> Putting it in glibc.inc definitely seems like a bad idea unless there is
>> evidence to suggest that all versions of glibc have this problem.
>> Nobody else has reported it previously, so I am guessing that either it
>> is specific to 2.9 or it is in some way unique to your system.
>
> I totally agree.
>
>> Assuming that it is a general problem with 2.9 then a better solution
>> would obviously be to find and fix the dependency problem.  Here's a
>> rough guide as to how to attack that:
>>
>> 1. Find the compile command that corresponds to the failing file
>> (setjmp.os or whatever it was).  Modify the command to replace -c with
>> -E and remove the "-o ..." option, then run it by hand.  This will
>> output the preprocessed source to standard output.
>>
>> 2. Inspect the preprocessed source to find out which symbol is not being
>> correctly defined.
>>
>> 3. Run a build without -j (so that it works) and then use grep to
>> establish which header file is meant to define the symbol in question.
>
> As you can see from the mails before the problem does not occur in the
> same file each time. I've made some clean(!) builds and have seen at
> least five different fails.  :(

it could also be some weirdness in the assembler. You could try using
different version of binutils-cross

>
> Steffen
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>




More information about the Openembedded-devel mailing list