This is the mail archive of the crossgcc@sourceware.org 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] |
anyone noticed an issue with gcc not installing the internal syslimits.h header file when doing a cross-canadian build ? the crosstool script doesnt seem to have anything to deal wtih this and the uClibc buildroot project has a workaround where it simply copies syslimits.h from the staging dir to the correct target dir ...
i looked through the gcc-3.4.4 build system and found this:
- gcc/Makefile.in will install syslimits.h only if fixincludes support is enabled (see the stmp-fixinc and install-mkheaders make targets)
- gcc/configure.ac disables fixincludes support if and only if $build != $host and the --with-sysroot option was not specified ...
so it seems like the special handling of syslimits.h which exists now in gcc/Makefile.in should be broken off from the fixincludes logic and always utilized (if that is possible ...) ?
a little googling found an old post from the master: http://gcc.gnu.org/ml/gcc/2002-08/msg00076.html
I haven't looked to see what his solution looked like or whether it still applies, but it at least looked interesting. - Dan
-- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html
------ 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] |