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] |
Kai Ruottu wrote: > > $prefix (=foo/myGCC). That works fine. Then I put the /usr/include > > tree from solaris into foo/myGCC/sparc-sun-solaris2.8/sys-include/ > > Please check what the aim for the '$prefix/$target/sys-include' is, > and what for the '$prefix/$target/include'... > > RTFM, "Standard Header Directories"... I think I'm the one responsible for giving him this advice. I concede didn't RTFM "System Header Directories". However, sys-include is *not* SYSTEM_INCLUDE_DIR; it is [CROSS_]SYSTEM_HEADER_DIR. The "--with-headers" configure option copies the path specified to sys-include. This directory is processed by fixincludes at build time. This is all correctly documented in the manual. The compiled-in directory search order for cross-compilers looks a bit odd, though: that might need some attention and/or fixing. I concede that I've gained more of my knowledge of cross toolchains from experimentation and reading the configure scripts rather than reading the manual. I'm welcome to correction or advice. Rup. ------ 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] |