[Top][All Lists]

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

Re: echo "enhancement" leads to confused legacy script tools...

From: Linda W
Subject: Re: echo "enhancement" leads to confused legacy script tools...
Date: Sun, 19 Mar 2006 17:29:11 -0800
User-agent: Thunderbird 1.5 (Windows/20051201)

Paul Eggert wrote:
Henrik Nordstrom <address@hidden> writes:

sön 2006-03-19 klockan 12:57 -0800 skrev Paul Eggert:

Autoconf deals with shells that do not conform to XSI, and where the
results are implementation-defined if there's a backslash anywhere in
the string, so to some extent this point is moot for Autoconf (though
it's undeniably a portability problem, one that is documented in the
Autoconf manual under "Limitations of Builtins").
I thought so too, but in this case it is a autoconf 2.57 output which is
failing, ending up with a lot of control characters instead of the
expected sed backreferences..

Autoconf 2.57 is pretty old.  Do you have the same problem with 2.59?
If not, then the problem's solved from the Autoconf point of view.
Otherwise, I'd ask you to try it with CVS Autoconf (which has further
fixes in this area).

        I already have 2.59 installed on my system, "2.59-80.1" from
SuSE9.3.  So it was with 2.59 autoconf that I originally ran into the


reply via email to

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