This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: cpp found limits.h in FIXED_INCLUDE_DIR, but not in STANDARD_INCLUDE_DIR
- From: Ian Lance Taylor <iant at google dot com>
- To: Jay <jay dot krell at cornell dot edu>
- Cc: <r0bertz at gentoo dot org>, <gcc at gcc dot gnu dot org>
- Date: Tue, 16 Sep 2008 07:03:18 -0700
- Subject: Re: cpp found limits.h in FIXED_INCLUDE_DIR, but not in STANDARD_INCLUDE_DIR
- References: <1221542711.12932.ezmlm@gcc.gnu.org> <COL101-W44D12B513798EC92C7C8AE64D0@phx.gbl>
Jay <jay.krell@cornell.edu> writes:
> While I believe I understand this build/host/target stuff fairly well,
> I do NOT know how to discuss it in a way that is understandable. :)
> There's (necessarily) too many compilers and no short clear way to refer to them.
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 system is of course only relevant when discussing
building the compiler, and becomes irrelevant once the compiler
exists.
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 is Windows or GNU/Linux; I can't
remember whether the OP said.
Ian