[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
broken line continuation in DOS files
From: |
Eric Blake |
Subject: |
broken line continuation in DOS files |
Date: |
Mon, 03 Sep 2001 10:50:14 -0600 |
I checked out the jikes compiler via CVS
(:pserver:address@hidden:/usr/cvs/jikes, password anoncvs,
module jikes). I'm using cygwin 1.3.2 on a Win98, with the drive
mounted in textmode, along with the latest cygwin release of automake,
unmodified:
$ automake --version
automake (GNU automake) 1.5
Written by Tom Tromey <address@hidden>.
[...]
The Makefile.am that comes with jikes has entries such as:
jikes_SOURCES = \
ast.cpp \
body.cpp \
...
Since my drive is mounted textmode, the cvs checkout puts \\\r\n
sequences in Makefile.am. However, automake reads the file in binary
mode, so it only recognizes \\\n as line-continuations. As a result,
the generated Makefile.in ends up looking like:
jikes_SOURCES = \
...
.PHONY: all ...
ast.cpp \
body.cpp \
...
And this causes make to issue the famous "*** missing separator. Stop."
error after configuration, since the makefile ends in a list of
filenames that do not form a rule.
I'm not sure where to make the patch, but it should be a simple matter
of telling automake to open Makefile.am in text mode, rather than binary
mode, or else treating \\\r, \\\r\n, and \\\n as equivalent line
continuations. I was able to work around the bug locally by stripping
out all \r from Makefile.am.
--
This signature intentionally left boring.
Eric Blake address@hidden
BYU student, free software programmer
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- broken line continuation in DOS files,
Eric Blake <=
- Next by Date:
咱们的家
- Next by thread:
咱们的家
- Index(es):