From: Sisyphus <sis...@op...> - 2006-01-07 08:01:57
|
----- Original Message ----- From: "Luke Dunstan" > > some other header ? I'm wondering whether inclusion of the > > '-ID:/MinGW/include' switch somehow makes the compiler conclude that > > headers > > located there (which includes stdint.h) are *not* system headers. > > Yes it does, because you are telling the compiler where to find them rather > than it using the internal default search paths. > Good - that's one more thing explained. Linux doesn't suffer this problem. If I specify something like '-I/usr/include' or even '-I/usr/bin/../include' gcc recognizes that this duplicates a system directory and just ignores it. I surmise that on my Win32 box, '-ID:/MinGW/include' is *not* ignored because gcc doesn't recognize that D:/MinGW/include is a duplication of the system directory D:/MinGW/bin/../lib/gcc/mingw32/3.4.4/../../../../include . Why does my MinGW installation list such strange paths ? It lists my include search paths as: #include <...> search starts here: D:/MinGW/bin/../lib/gcc/mingw32/3.4.4/../../../../include D:/MinGW/bin/../lib/gcc/mingw32/3.4.4/include /mingw/lib/gcc/mingw32/3.4.4/../../../../include /mingw/include /mingw/lib/gcc/mingw32/3.4.4/include /mingw/include Is there some way of making that cleaner ? It should only need to list the following: D: /mingw/include D:/mingw/lib/gcc/mingw32/3.4.4/include Cheers, Rob |