On Thu, Mar 17, 2005 at 11:44:40AM -0500, Christopher Faylor wrote: >On Thu, Mar 17, 2005 at 11:32:23AM -0500, Paul Stodghill wrote: >>If a program includes <float.h> and is compiled with gcc -mno-cygwin, it >>appears to include the wrong instance of float.h. More specifically, >>"/usr/i686-pc-mingw32/include/float.h" is written assuming that it will >>be included before "/usr/lib/gcc/i686-pc-cygwin/3.4.1/include/float.h" >>and uses #include_next to pick up the compiler provided definitions. >>However, this does not appear to be happening. >> >>The reasons appears to be that the >>"/usr/lib/gcc/i686-pc-cygwin/3.4.1/include" appears on the search path >>before "/usr/i686-pc-mingw32/include". Adding >>"-I/usr/i686-pc-mingw32/include" to the command line does not work >>because it is suppressed as a duplicate entry. > >There aren't supposed to be any "cygwin" directories in the search path. >Apparently this part of gcc is busted. > >Gerrit?
Just to clarify: there aren't supposed to be cygwin directories in the include (or lib) search path when -mno-cygwin is specified. Obviously (to me anyway) they should be there when that option is not used. This is handled by the cygwin-specific .c files in gcc/config/i386/ . cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
