Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Wed, 2 Oct 2002 10:09:20 -0400
From:	Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: CR/NL problem with cpp.exe
Message-ID:	<20021002140920.GA12462@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CHEDKHJJDLOCCOFLMGEAGEACCNAA DOT dvasaru AT broadpark DOT no> <001501c26a0c$38db6790$2a00a8c0 AT dash>
Mime-Version:	1.0
In-Reply-To:	<001501c26a0c$38db6790$2a00a8c0@dash>
User-Agent:	Mutt/1.4i

On Wed, Oct 02, 2002 at 08:07:03AM -0400, Kris Warkentin wrote:
>I agree.  It's just that the util I'm looking at is GNU cpp, which DOES have
>a cygwin specific port but doesn't seem to deal with the CRLF problem.  So
>we've got the situation that, for whatever reason, it doesn't look like all
>the Cygwin changes were rolled into the public branch which is the puzzle.

This is correct.  All of the cygwin changes were not rolled back into 2.95.
Some of them were submitted and never approved.  Some were not approved.

As soon as we officially release gcc 3.2, I plan on trying to get the gcc
changes applied to the gcc mainline.  It will be a long road ahead, though.

In the meantime, the sources that were used to build gcc are available
for download.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -