Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-Id: <200003280434.WAA18089@hp2.xraylith.wisc.edu>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: net release/installer status? 
In-reply-to: Your message of "Tue, 28 Mar 2000 04:04:08 +0200."
             <38E01318 DOT 5EA4BD9 AT vinschen DOT de> 
Date: Mon, 27 Mar 2000 22:34:41 -0600
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>

Corinna Vinschen <corinna AT vinschen DOT de> writes:
> FYI: I finally could cross compile cygwin1.dll on my linux box.
> Ah, yes, it's not only compiled but it also runs under W2K.
> 
> Nevertheless I have some trouble. I have patched two Makefiles and
> I had to configure twice in winsup. Eventually I couldn't compile
> the utils subdir because w32api/include isn't in the configured
> incude path list.
> 

The problem may actually be quite simple -- we may be lacking 
  -nostdinc -I<path_to_w32ap_include> 
in the Makefiles. The -B<path_to_newlib> only handles the newlib
includes, but the w32api headers are still coming from your
installed tree.

I remember running into this when I had an older version of w32api
and gcc installed, and tried an one-tree build. I should dig it
up and submit a patch for it.

Regards,
Mumit