Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Textmode mounts broken in cygwin 1.5.10-3
Date: Tue, 8 Jun 2004 17:39:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <40C5EA1D.2030209@gmx.net>
Message-ID: <NUTMEG3sl3xbYiMCIqt0000023f@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 08 Jun 2004 16:39:34.0875 (UTC) FILETIME=[2E6FEAB0:01C44D77]

> -----Original Message-----
> From: cygwin-owner On Behalf Of W. Tuchan
> Sent: 08 June 2004 17:32

> 
> > 
> > It's not a known problem of gcc.  gcc should not care about 
> text mode
> > mounts.  It is supposed to work correctly with any mount modes.
> > 
> 
> 
> Sorry, maybe it was a problem of gcc. I'm still useing gcc 2.95.3.

  Yes, 2.95.3 had a problem with CR+LF line ends; yes, it has been fixed in
3.0.something, I think the new preprocessor took care of it.

  In fact IIRC, even in 2.95.x it was only a problem on continuation lines,
because the code that looked for backslash-LF and concatenated the lines
didn't recognize the sequence backslash-CR-LF, but all other source lines
were ok with CR-LF line ends.

  But yeh, it's an old and long-gone problem these days.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/