On Sun, 2002-05-19 at 14:25, J.A. Magallon wrote: > It can be because gcc just does that, It 'fixes' system headers to > correct some odd things, and stores its modified versions in, say, > /usr/lib/gcc-lib/3.1.0/include. So default includepath for gcc is > really -I/usr/lib/gcc-lib/3.1.0/include -I/usr/include. > (the full real path for 3.1 is: > /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.1/include) > > > Then if you put by hand /usr/include again, you are forcing gcc to > get the faulty headers again. So it should not be done.
Wouldn't it make more sense to fix the "faulty" headers? -- TTFN, Lonnie Borntreger
