Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-Id: <4.3.1.2.20000413120152.00d8f1b0@pop.ma.ultranet.com>
Date: Thu, 13 Apr 2000 12:04:18 -0400
To: Mo DeJong <mdejong@cygnus.com>,
        "cygwin@sourceware.cygnus.com" <cygwin@hotpop.com>
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Subject: Re: Mingwin does not seem to know where its headers live.
In-Reply-To: <Pine.LNX.4.10.10004130842580.27294-100000@abomination.cygn
 us.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

You need to set gcc up to recognize a MINGW type compile rather than a 
Cygwin compile.  You can't mix and match Cygwin stuff and MINGW stuff.
You need to play with your specs file some as I recall.  Check the mail
archives and/or Mumit Kahn's site for details...

Larry


At 11:46 AM 4/13/00, Mo DeJong wrote:
>I am trying to compile this code.
>
>BASH.EXE-2.03$ cat WIN32.C
>#include <string.h>
>#include <direct.h>
>
>int main(int argc, char ** argv) {
>     strcpy(NULL,NULL);
>     mkdir(NULL);
>     return 0;
>}
>
>
>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
>
>But, if I provide the fully qualified path name
>of mingwin's header directory it compiles.
>
>BASH.EXE-2.03$ gcc -mno-cygwin -c WIN32.C
>-I/usr/i686-pc-cygwin/include/mingw
>
>
>Why does mingwin not know where its own
>headers live? Am I doing something wrong?
>
>Mo Dejong
>Red Hat Inc.
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com