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]

Q: What is customary wrt GCC's include-fixed?

Hi!

I've managed to build a fine new toolchain based on GCC v4.3.2 and uClibc
v0.9.30.  Now, I've noticed that GCC today create a separate include-fixed
directory for "fixed" includes, whatever that means.  What is customary
for using the files therein?

Should I symlink/move everything from include-fixed/ to include/ or should
I add -isystem ...include-fixed to my build system?

The file in question that triggered this is limits.h, which is #include_next
included from uClibc's limits.h:

armeb-redfox-linux-uclibc-4.3.2/lib/gcc/armeb-redfox-linux-uclibc/4.3.2/include-fixed/limits.h

Regards
 /Jocke

--
For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]