Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <4.3.1.2.20000413120152.00d8f1b0@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 13 Apr 2000 12:04:18 -0400 To: Mo DeJong , "cygwin AT sourceware DOT cygnus DOT com" From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Mingwin does not seem to know where its headers live. In-Reply-To: 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 >#include > >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 AT sourceware DOT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com