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: <200003030733.BAA11368@hp2.xraylith.wisc.edu>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: 'cygwin-net-485' snapshot win32 headers problem 
In-reply-to: Your message of "Thu, 02 Mar 2000 14:19:05 EST."
             <20000302141905 DOT A20997 AT cygnus DOT com> 
Date: Fri, 03 Mar 2000 01:33:58 -0600
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>

Chris Faylor <cgf AT cygnus DOT com> writes:
> 
> Thanks very much for looking into this.  Also, for the record, a failure
> of gcc in the cygwin net release to perform any kind of cross compilation
> should not be considered a show-stopper for the net release.
> 
> I don't want to give the cygwin release any more dependencies than it
> already has.
> 
> That is not to say that we should not try our best to fix problems that
> we've discovered, if we can.

That's the goal -- point out the problems, and hopefully the person having
problem will submit a bug report, perhaps with a fix, to gcc maintainers
for that particular (non-x86-win32) port.

The compiler and binutils code is frozen unless we uncover crippling bugs
in pe-coff support.

Regards,
Mumit