Re: glibc_2.9 compile failed for armv5te

[Steffen Sledz <sledz@dresearch.de>]

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.  :(

Steffen