Re: cpp found limits.h in FIXED_INCLUDE_DIR, but not in STANDARD_INCLUDE_DIR

2008-10-07 Thread Zhang Le
Hi, all, I think I've found the reason. It all comes from this gentoo patch: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-devel/gcc/files/4.1.0/gcc-4.1.0-cross-compile.patch?rev=1.1&view=markup Specifically: -elif test "x$TARGET_SYSTEM_ROOT" != x; then +elif test "x$TARGET_SYSTEM_ROOT"

Re: cpp found limits.h in FIXED_INCLUDE_DIR, but not in STANDARD_INCLUDE_DIR

2008-09-20 Thread Eus
Hi Ho! --- On Fri, 9/19/08, Ian Lance Taylor <[EMAIL PROTECTED]> wrote: > Eus <[EMAIL PROTECTED]> writes: > > >> In this case the end result is an x86-build > native-MIPS compiler. > >> This requires first building an x86-x-MIPS > copmiler. Of course in > >> practice it matters whether x86 here

Re: cpp found limits.h in FIXED_INCLUDE_DIR, but not in STANDARD_INCLUDE_DIR

2008-09-19 Thread Eus
Hi Ho! On Tue, 9/16/08, "Ian Lance Taylor" <[EMAIL PROTECTED]> wrote: > HOST-x-TARGET == cross-compiler > native-HOST == native compiler > BUILD-build native-HOST == native compiler built by cross-compiler > BUILD-build HOST-x-TARGET == cross-compiler built by cross-compiler > > The BUILD-build