This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Dan Kegel wrote: > That's quite right. I suppose I should add a cautionary note to > the crosstool doc laying out the issues Kai mentions, so newbies > know that their target may set constraints on tool versions. Being a definite newbie in this area I'm now wondering about several cross compilers I've built for a product we have. I'm targeting i386-pc-solaris2.6, sparc-sun-solaris2.5.1, powerpc-ibm-aix4.2.1.0 and i586-pc-linux-gnu. Because I copied the libs and headers from the original hosts and I'm using C only (no C++) I have assumed that the backwards compatibility problems Kai described will not affect me, but is that safe to assume? I did have to build glibc to build GCC (3.2), but I have been under the impression that this was an internal compiler thing and wouldn't affect output binaries...? In summary I'm asking: If I use the hosts original libs and headers, and only use C (no C++) am I still going to be affected by backwards compatibility problems with the compiler/glibc and thus should rather be using GCC 2.95 with an older glibc? Thanks, -Nathan ________________ Hummingbird Ltd. Toronto, Canada ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |