This is the mail archive of the
mailing list for the Cygwin project.
Re: Mingwin does not seem to know where its headers live.
- To: Mo DeJong <mdejong at cygnus dot com>, cygwin at sourceware dot cygnus dot com
- Subject: Re: Mingwin does not seem to know where its headers live.
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Thu, 13 Apr 2000 09:32:36 -0700 (PDT)
- Reply-To: earnie_boyd at yahoo dot com
--- Mo DeJong <email@example.com> wrote:
> When I build with mingwin, it bails out
> saying it can not find direct.h.
> BASH.EXE-2.03$ gcc -mno-cygwin -c WIN32.C
> WIN32.C:2: direct.h: No such file or directory
I'm going to get picky here. Using Cygwin gcc with the -mno-cygwin switch is
not MinGW. There is a different gcc which Mumit distributes that is native to
Win32 and thus is the MinGW GCC toolset. You can get this from the pointers at
Using the -mno-cygwin switch is sort of a cross compile. You have a separate
set of headers, a separate set of libraries and a special switch which is
controlled via the specs file.
Mumit has on his site a "howto" for using the -mno-cygwin switch successfully.
This information is in the volumes of archives.
Earnie Boyd: <mailto:firstname.lastname@example.org>
__Cygwin: POSIX on Windows__
Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html>
__Minimalist GNU for Windows__
Mingw32 List: <http://www.egroups.com/group/mingw32/>
Mingw Home: <http://www.mingw.org/>
Do You Yahoo!?
Send online invitations with Yahoo! Invites.
Want to unsubscribe from this list?
Send a message to email@example.com