Remember the
>./libgcc2.c:41: stdlib.h: No such file or directory
error when building gcc-2.95.1?
The solution was to:
-------
Edit gcc/config/arm/t-linux and add "-Dinhibit_libc" and
"-D__gthr_posix_h" to TARGET_LIBGCC2_CFLAGS
Delete #include "gthr.h" in libgcc2.c
Add the "--disable-threads" option to configure
-------
However these consequences worried me:
>>1) What effect will the "inhibit_libc", "__gthr_posix_h", and
>>"--disable-threads" options have on my compiler?
>
>The generated libraries will not be thread safe. This will bite you if, for
>example, you have a multithreaded C++ program that uses exceptions.
So as I need a fully functionnal toolchain, I asked:
>>Or what about building gcc with "inhibit_libc", --disable-threads, etc.,
>>and again build/install glibc for arm, rebuild gcc with the new arm header
>>and whitout the "inhibit_libc", --disable-threads, etc.?
Philip Blundell's answer:
>This is the correct way to solve the problem.
So my last question about this is:
Once, after glibc has been built, gcc is built for the second time without
the "inhibit_libc", "__gthr_posix_h", and "--disable-threads" options, do I
need to rebuild glibc as well for all the libraries to be thread safe, or is
only rebuilding gcc sufficient ?
Thanks!
And have a good day!
--
Fran�ois Desloges
[EMAIL PROTECTED]
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
