CRLF and CVS (was RE: guru needed -- diagnosing configure problems on Win32)


Subject: CRLF and CVS (was RE: guru needed -- diagnosing configure problems on Win32)
From: Paul Rohr (paul@abisource.com)
Date: Fri Jan 28 2000 - 12:20:40 CST


At 12:14 PM 1/28/00 +0100, Henrik Berg wrote:
>I have one qlue, I'm using my Linux to do the cvs, so my source is in LF
>text, as opposed to CRLF text. The Cygwin should be handling this problem,
>but it could be a qlue.

Oh, so *that's* where those problems are coming from. I'm not sure whether
this is related to the build problems or not, but this is *definitely* worth
fixing anyhow.

Specifically, I've noticed recently that some of the files you've been
touching have mixed-up line endings. For example, see:

  abi/src/other/spell/newMain.c

The various CVS clients do a good job of converting between the "local"
linefeed conventions for your platform and the "canonical" linefeed
convention stored in the repository. However, this mechanism gets confused
if you try to commit files with the wrong linefeed convention.

Thus, for example, if I want to apply a patch written on Unix from a Win32
CVS client, I'd have to fix the linefeeds before checking it in. Usually
there's an uncompress switch that'll do that for me, but I've also been
known to FTP plain text files twice (once as binary and once in text mode)
just to get everything fixed up properly.

It sounds like your problem might be the other way around, but it shouldn't
be hard to fix.

Paul

PS: Do any of the script wizards on the list have a handy-dandy way to
detect and/or fix files which already have mixed-up linefeeds?



This archive was generated by hypermail 2b25 : Fri Jan 28 2000 - 12:15:18 CST