This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
:-(From what I gather by reading the INSTALL (and FAQ) files from the
source archives I would need to build glibc separately, after I built
binutils, use the same prefix and probably specify the
"--with-headers" option as well. I take it glibc won't be relying on
the GCC cross-compiler otherwise we have a chicken-and-egg scenario on
our hands?
There is a chicken-and-egg scenario.
What does constitute a "vanilla cross-compiler"? Is this a "limited" cross-compiler without the glibc dependencies (because that is the only way I think possible to have glibc and a fully-fledged cross compiler the way I want it)?You need to first build a vanilla cross-compiler without building the library.
You need to use that toI see, thought as much. Small steps and all that!
build glibc. Then you need to use glibc to build the full
cross-compiler.
I've just downloaded the headers, but (see below) I think I found exactly what I was looking for...Finally, in the same file there is mention that I would also need the
header files for the Linux arch (presumably the target arch as I
already have the host ones installed) - is that really a requirement?
As far as I know, it is a requirement.
W-H-A-T a gem that crosstool.sh file is (provided it works though)!Also, I take it it is not possible to build glibc at the same time I
build GCC (i.e. by dropping the source tree into the GCC main tree),
right?
Right.
Anyhow look at http://kegel.com/crosstool/ .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |