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] |
Terve Kai!More likely a "feature", the 'libc.a' for the $target should be used, not that for the $host,
Sorry for the typos, I was writing this out of the top of my head and I was tired then.
Reading your two posts, are you saying this could be a bug in the GCC sources?
To answer your questions:This "some kind of" GCC is the final GCC !
> What on earth "first stage gcc"?
I understand that the idea of building a cross-compiler would be:
1. Build a cross-binutils for the target platform. 2. Build some kind of cross-gcc for the target platform.
3. Use that cross-gcc (in some howtos referred to as 1st-stage GCC) to build a glibc for the target platform.The C library being used by the produced GCC is the proprietary AIX C library in this case.
4. Re-build GCC with itself.As one more "code red" practice for new recruits, producing first a native GCC from just the
Are you saying I need a AIX C library on my Linux host system in order to be able to build a Linux hosted cross-compiler for AIX? Why?
Putting it below some thought-out $sysroot and pointing to it using '--with-sysroot=$sysroot'> I didn't use the '--with-sysroot=$sysroot' to point to the > (unexisting) AIX5.3 C library...
What is that business? Would you have a pointer to dome f* manual I could use to educate myself? Even if the AIX C library is not freely available, I could get a hold of one, but what would I have to do with it?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |