Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Thu, 26 Oct 2000 14:04:25 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT sources DOT redhat DOT com
Subject: New GCC test release available
Message-ID: <20001026140425.C32324@redhat.com>
Reply-To: cygwin AT sources DOT redhat DOT com
Mail-Followup-To: cygwin AT sources DOT redhat DOT com
References: <OFEB1DB119 DOT 4FC45371-ON85256984 DOT 0060D63E AT raleigh DOT ibm DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i
In-Reply-To: <OFEB1DB119.4FC45371-ON85256984.0060D63E@raleigh.ibm.com>; from egb@us.ibm.com on Thu, Oct 26, 2000 at 01:39:48PM -0400

On Thu, Oct 26, 2000 at 01:39:48PM -0400, Ed Bradford/Raleigh/IBM wrote:
>If I knew which list to send email to I would try to prevail on the gcc/cpp
>owner to fix the problem.  Apparently, it sees
>     LF
>     CRLF
>ok, and
>     \LF
>ok, but
>     \CRLF
>gets broken.  It seems like an easy fix.  That way people wouldn't have
>to worry about the exact format of header files in /usr/include.

Gee.  You'd "prevail", would you?  You're willing to take time to "prevail"
but not to investigate the problem and provide an "easy" fix?

How helpful.

Well, coincidentally, I have recently asked DJ to look into a fix for
gcc.  He's provided one and I've generated a new, test release with his
patch.  It is now available on mirrors.

This is a test version of gcc, so you have to choose it appropriately
when running setup.exe.

The only fix in this release is the CRLF problem in cpp.  There are no
other changes from the previous version.

Ironically, the version of gcc that we ship to customers has had this
problem fixed already.  So, I actually scheduled DJ's time to work on
this net release issue.  But, I'm sure that is exactly what everyone
expects.  After all, doesn't Red Hat have a staff of engineers devoted
to nothing else but scanning the cygwin mailing list and listening to
user gripes?

Anyway, please send success or failure reports to the mailing list.  If
this solves everyone's problems, I'll remove the "test" distinction.

You're welcome, by the way.

cgf

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