On Thu, 19 Feb 2004, Thomas Dickey wrote: > On Fri, 20 Feb 2004, Henry Nelson wrote: > > No - it's assuming that the files are in <ncursesw/xxx>. If I'd put > curses.h in /usr/local/include rather than /usr/local/include/ncurses > or /usr/local/include/ncursesw, then gcc picks up that ahead of the > /usr/include/curses.h - not good if you're allowing for building with > either flavor of curses. Adding -I/usr/include "fixes" it - if the > program doesn't happen to use some of gcc's "fixed" includes(*). > > (*) "fixed" includes originally ANSIfy'd system headers to make gcc run > better. But it doesn't really do that any more - except as an > afterthought, since gcc's extensions & non-standardisms are what I see > in the "fixed" includes.
Yes, I think it stopped with 3.3. Since then it didn't "fix" any includes. Here it only added a syslimits.h. -- http://www.pervalidus.net/contact.html ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
