gcc 3.2's cpp breaks configure scripts

[Gareth Pearce]

>
>On Thu, Aug 01, 2002 at 07:03:43AM +0000, Gareth Pearce wrote:
> > but only with files which are fixincluded right? (not rhetorical)
>
>This has nothing to do with fixinclude. #include_next is used e.g.
>to include gcc's include header of the same name, or by libstdc++-v3
>headers to include C headers, etc.
>Also, -I/usr/include changes the status of /usr/include headers from
>system headers to user headers, thus you may get warnings (or errors
>with -Werror) where you otherwise would not get any.


Hmmm I think the lights starting to seep into my brain...  But just to be 
sure,
your saying that adding -I/usr/include (or similar) can cause libstdc++ 
headers to break due to the way they use #include_next?  If so then I guess 
its the rough road or no road...(too many special cases for my liking)  hmmm 
time to bug someone else then I guess :)

Gareth

_________________________________________________________________
Join the worldÂ’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com