From:	"Juan Manuel Guerrero" <ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De>
Organization:	Darmstadt University of Technology
To:	pavenis AT lanet DOT lv
Date:	Fri, 7 Sep 2001 14:43:28 +0200
Subject:	Re: Problem with sed3028b.zip
CC:	djgpp-workers AT delorie DOT com, djgpp-workers AT delorie DOT com
In-reply-to:	<3B97BFC5.20768.6D2E5D@localhost>
X-mailer:	Pegasus Mail for Windows (v2.54DE)
Message-ID:	<6745033395E@HRZ1.hrz.tu-darmstadt.de>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 6 Sep 2001 18:26:13 +0300, Andris Pavenis wrote:
> Makefile in directory gcc after running configure contains CR CR LF in one line after '\'.,
> make invokes bash at that place and bash fails. Downgrade to sed-3.0.2 fixes the problem
> (I'm getting CR LF there as it should be)

Please elaborate a little bit more. What sed script causes this? What lines in the makefile
that are terminated with backslash are brocken? Are all lines that are terminated by a backslash
affected by this misfeature?

Only FYI: I have used the following very naive test file:

bar\
foo\
bar

and run the sed command:

"s/bar/rab/;s/foo/oof/"

I have inspected the produced file with a hex-editor. The file
is completely ok. Especially, all backslashes are followed *only*
by CR LF. This is independent of the EOL used in the source file.

Regards,
Guerrero, Juan Manuel

- Raw text -