>Phil mentions that this is a common problem when building cross-compilers for
>the first time. After compiling with the --disable-threads
>and the commented out thread include files, do I need to recompile things a
>second time (without the --disable-threads flag and with the
>thread include files) ? Why will things be different this time?
Sorry, I wasn't entirely clear there. The problem you have occurs because you
don't have a complete target build environment set up when you build the
compiler, so the C library header files and libraries are not available. Once
you have built the compiler for the first time, you can use it to compile the
C library for the target system and make this available for subsequent
rebuilds of the compiler.
So the answer is that when you compile the second time you will hopefully be
doing so in a more complete system and so things should "just work".
>(The code that I wish to compile with the cross-compiler includes the use of
>threads).
In this case you will definitely need to install libc.
>Does anyone know if this is likely due to a bugfix in the compiler (was
>anything like this addressed?), or is it *random chance* that
>this bug got fixed (or just hidden)?
It's virtually impossible to say. A large number of bugs have been fixed
since egcs 1.1 was forked. The C++ compiler in particular is much better
now. Maybe someone else reported your bug or a similar one and it was fixed;
maybe the code in question was rewritten for some other reason and the bug
eliminated; maybe the bug is still potentially there but the conditions that
trigger it simply don't arise with your code now. All I can suggest really is
that you wait to see if the bug returns, and if so report it to the egcs-bugs
list.
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
