Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <000301bfd590$185d2e30$0100000a@TIMYX18EWDT6RQ>
From: "Tim Prince" <tprince@computer.org>
To: <cygwin@sourceware.cygnus.com>
References: <3946AB9D.EB4652BE@objectcentral.com> <20000613181334.A17964@cygnus.com>
Subject: Re: Supporting Open Source software
Date: Tue, 13 Jun 2000 16:02:10 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


Tim Prince
----- Original Message -----
From: "Chris Faylor" <cgf@cygnus.com>
To: "cygwin newsgroup" <cygwin@sourceware.cygnus.com>
Sent: Tuesday, June 13, 2000 3:13 PM
Subject: Re: Supporting Open Source software


> We've already said that the person who would normally look into this
> problem has been on an extended leave of absence from this mailing
> list.  We have always relied heavily on Mumit to fix this kind of
> problem in the past and his absence has left a huge void.
>
At the very least, it has been helpful to have Mumit evaluate the
information we have gathered and submit a patch to gcc.  Many changes
are being made to gcc nowadays without considering what they do on
targets other than the ones of interest to the submittor, and we don't
want to (won't be permitted to) do the same from the cygwin side.  In
fact, many of us depend on having things work the same on cygwin and
other targets.
>
> The basic problem is THERE IS NO ONE AVAILABLE WHO UNDERSTANDS GCC
WELL
> ENOUGH TO FIX THE PROBLEM QUICKLY.
>


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