Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <200004182049.PAA12440@hp2.xraylith.wisc.edu>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: [net release] solution to -mno-cygwin problem
Date: Tue, 18 Apr 2000 15:49:10 -0500
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>

Thanks to a lovely cold, and I'm home with time to install the new net
release, and of course the first thing I tried was to reproduce the 
-mno-cygwin problem reported lately.

Here's the symptom: when you -mno-cygwin, gcc should be looking in mingw
include directory first, but it's not.

The problem: We somehoe mixed up the name mingw and mingw32, and things
have gotten confused. GCC is looking for a directory named:
  
  /usr/i686-pc-cygwin/include/mingw32

whereas the directory is named:

  /usr/i686-pc-cygwin/include/mingw

in the net release. Something that will fixed soon.

The solution is any one of the following three:

1. Symbolically link the following:
   
   $ cd /usr/i686-pc-cygwin/include
   $ ln -s mingw mingw32

This is what I've done locally.

2. Rename the directory:

   $ cd /usr/i686-pc-cygwin/include
   $ mv mingw mingw32

Just as easy.

3. Edit the gcc specs file (`gcc -print-file-name=specs'), taking care
   not to wrap any lines and so on, and change `mingw32' to `mingw' in
   the:
     -iwithprefix ../../../../include/mingw32 
   to
     -iwithprefix ../../../../include/mingw

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com