>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.
>2) Would it be better to add a "-D/usr/include" instead the the above
>defines? I am building a gcc cross-compiler for an ARM Linux system on an
>Intel Linux box. Will the system header files be close enough, or should I
>not take this chance?
You would probably get away with this most of the time, but it's probably not
a good idea.
>3) Finally, I think the reason I hit this problem is that the Linux source
>base does not contain all the header files I need (such as stdlib.h,
>unistd.h, etc.). Why are these files not in the Linux kernel source base?
>Where do they come from?
They are part of the C library. I think Chris Rutter's notes explain how to
bootstrap a cross-compile environment from scratch, including how you can get
the right headers in place.
p.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
