Mail Archives: cygwin/2002/02/06/16:43:53
On Wed, Feb 06, 2002 at 09:31:55PM +0000, Ben wrote:
>I am having major problems with include files in cygwin. Firstly, I cant
>include files which are linked (.lnk files (symlinks?). This works fine
>on bash under redhat. This isnt my main problem though...!
>
>The main problem is that I can tget the -I flag to work correctly under
>cygwin. Take a look at this:
>
>Cygwin:-
>
>bash-2.05a$ gcc asd.cpp -I/tmp -v
>
>#include "..." search starts here:
>#include <...> search starts here:
> c:\program
>files\devcpp\bin\..\lib\gcc-lib\i386-mingw32msvc\2.95.2\..\..\..\..\include
>End of search list.
>
>
>
>Linux:-
>bash-2.05a$ gcc asd.cpp -I/tmp -v
>
>#include "..." search starts here:
>#include <...> search starts here:
> /tmp
> /usr/local/gcc-3.0/include/g++-v3
> /usr/local/gcc-3.0/include/g++-v3/i686-pc-linux-gnu
> /usr/local/gcc-3.0/include/g++-v3/backward
> /usr/local/include
> /usr/local/gcc-3.0/lib/gcc-lib/i686-pc-linux-gnu/3.0/include
> /usr/include
>End of search list.
>
>
>The linux one is adding /tmp to the list of directories to be searched.
>Why isnt cygwin? The redhat gcc is version 3, whereas the one on my
>machine is 2.9 something, but I dont think its that...!
>
>Hopefully someone can help with this?!
It looks like you're actually trying to use a *mingw* version of gcc.
Mingw is officially supported by the folks at www.mingw.org.
If it is really a mingw version of gcc, that certainly explains why
it can't resolve cygwin paths or symlinks. You need a cygwin version
of gcc to understand cygwin paths and cygwin symbolic links.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -