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] |
>> Has anyone else seen this for other cross targets, and does *anyone* >> have an idea how to best get past this? > > Maybe we should bomb the GCC-developers with bug reports about the >misuse of the '$prefix/$target/sys-include' now... During the last >years I have now and then try to report this, but with no response >at all... > > The current workaround I now use is to symlink all those checked >headers: 'stdlib.h', 'unistd.h', 'string.h' and 'limits.h' into >'$prefix/$target/sys-include' from '$prefix/$target/include', so >that they will not be replaced with stubs during the GCC-build. Is that after you build/install newlib? I looked after building bootstrap, and $prefix/include is empty, and $prefix/$target/sys-include doesn't contain any header files. -- Peter Barada peter@baradas.org ------ 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] |