[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: carriage return line endings vs. literal ^M in status.m4

From: Ralf Wildenhues
Subject: Re: carriage return line endings vs. literal ^M in status.m4
Date: Sat, 5 Apr 2008 13:30:35 +0200
User-agent: Mutt/1.5.17+20080114 (2008-01-14)

* Jim Meyering wrote on Sat, Apr 05, 2008 at 01:14:30PM CEST:
> Just got a clarification (stale Subject was misleading).
> This is for OS/2 ( Ecs v2 rc4), not Maemo/OS2008.


> Elbert just replied privately.
> My patch didn't help.
> It's failing with sed's unterminated `s' command,
> which makes me think this related code is the true culprit:
> cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
> sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g" < "$tmp/subs1.awk" > 
> "$tmp/subs.awk" \

Sounds like it, yes.

> When $ac_cr is ^M on a system where that is also the EOL marker,
> that's exactly the error you'd get,

How do we find out portably whether carriage return is the EOL marker?
In that case we should skip the above sed script.

> Now, I wonder  if this is a fundamental violation of assumptions.

Dunno, but I don't think this will be the last issue found on this
system.  IOW, testing should be iterated until we have something that
really works.

Unfortunately, that may mean that what we have in the end may need to be
retested on other systems.  Not sure what to decide for 2.62 here, but
if Eric has a preference I would certainly respect his decision on this


reply via email to

[Prev in Thread] Current Thread [Next in Thread]