This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem including float.h with gcc -mno-cygwin (Danny can you comment?)
- From: Danny Smith <dannysmith at clear dot net dot nz>
- To: Cygwin <cygwin at cygwin dot com>
- Date: Sun, 20 Mar 2005 09:21:42 +1200
- Subject: Re: Problem including float.h with gcc -mno-cygwin (Danny can you comment?)
- Reply-to: Danny Smith <dannysmith at users dot sourceforge dot net>
cgf wrote:
>On Sat, Mar 19, 2005 at 11:14:04AM -0500, Paul Stodghill wrote:
>>
>>[The fact that the cygwin compiler path appears on the search path] is a
>>different and unrelated problem, I think.
>>
>>barney-xp$ md5sum /usr/lib/gcc-lib/*/3.3.3/include/float.h
>>248cb979b88c788e88100b913eea6ce9
>>*/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/include/float.h
>>248cb979b88c788e88100b913eea6ce9
>>*/usr/lib/gcc-lib/i686-pc-mingw32/3.3.3/include/float.h
>>barney-xp$
>>
>>The bug that I am observing is that /usr/i686-pc-mingw32/include needs
>>to appear on the search path before any of the /usr/lib/gcc-lib include
>>files.
>
>That would make mingw unlike every other compiler out there. Try it on
>linux and you can see that the gcc library includes are supposed to be
>first. Putting them second would screw up other things.
>
>Danny, are you reading this?
On native mingw build I get this:
#include "..." search starts here:
#include <...> search starts here:
D:/MINGW/BIN/../lib/gcc/mingw32/3.4.3/../../../../include
D:/MINGW/BIN/../lib/gcc/mingw32/3.4.3/include
D:/MINGW/BIN/../lib/gcc/mingw32/3.4.3/../../../../mingw32/include
/mingw/lib/gcc/mingw32/3.4.3/../../../../include
/mingw/include
/mingw/lib/gcc/mingw32/3.4.3/include
/mingw/lib/gcc/mingw32/3.4.3/../../../../mingw32/include
/mingw/include
End of search list.
As far as I can remember (gcc 2.95.3) the mingw include dir has preceded the
gcc include dir.
Danny
>
>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/