Thomas,
Sorry if I was unclear. I am using "^M" here to represent the single
byte with an ASCII value 0x0D / 13 decimal, carriage return. I was not
referring to the escape sequence "^" plus "M".
status.m4, and thus resulting 'configure' scripts, contain that byte,
even though all lines are terminated with 0x0A / 10 decimal, linefeed.
tr would work (or an awk builtin? But, awk is what is being detected
here) on ASCII-based systems. Non-ASCII-based systems would be easy
enough to detect, though.
-s
Thomas Dickey wrote:
On Mon, 27 Oct 2008, Steven R. Loomis wrote:
Hello,
autoconf 2.63 has worked well for our project (icu), except for an
issue with a bare carriage return (hereafter '^M') in status.m4 which
shows up in resulting configure scripts. The line in question is:
ac_cr='^M'
If I am not misreading the git repository, the current development
version also has such a line.
I found and read this discussion:
http://lists.gnu.org/archive/html/autoconf-patches/2008-04/msg00007.html
but, most of the later discussion seemed to be about preferring \r in
the output form over ^M.
That might not be portable enough (one workaround would be to use "tr"
to construct the character from less troublesome text).
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
