In other words, tr has been used in configure scripts long before this
particular autoconf patch to config.status.
Yes, I gathered that. What I was confused about was your message
referred to using \r, but the Texinfo config.status was using $as_nl
(not $as_cr). That made me think there were other uses of tr that the
Texinfo config.status was not exercising. Which I guess is indeed the
case.
Solaris /usr/ucb/tr
Well, Solaris /usr/ucb/anything has never been anything but trouble.
that we already had problems trying either \015 or \r in awk.
Ok. I'm surprised.
And literal ^M in the file was also problematic.
Of course.
It's used in multiple contexts in configure scripts. Gnulib has several
macros that assume tr availability.
...
I don't see any reason to single out tr
The only reason I was resisting was because your original msg implied
there was a single use of tr in configure. If that were the case, it
seemed like it would be simpler to do something else. But now it's
clear that's not the case. So fine. I'll ask rms about adding it.
but wouldn't mind seeing a disclaimer pointing to the autoconf
manual on common tool portability issues.
I believe it's already there.
Thanks,
Karl
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
