On Oct 30, 2007, at 1:26 AM, Martin Costabel wrote:
> That is, it interprets the escaped backslashes plus the following
> character as escape sequences. This is a buggy implementation not of
> POSIX conformance, but of XSI extensions of the POSIX standard, see
> <http://www.opengroup.org/onlinepubs/009695399/utilities/echo.html>
> It is a pity that Apple went this way. For the moment we can complain
> and file bugs, but we have to live with it.
>
> Several workarounds are possible:
> - Replace every "echo " by "/bin/echo " in configure
> - Replace in the first line of configure sh by bash
> - Change the failing echo command lines so that they don't use
> backslashes as escape sequences, i.e. replace the one-liner by several
> lines.
I'm not a frequent contributor, and may be missing something here,
but doesn't the open group web page hint that 'echo' is deprecated
and the use of 'printf' is encouraged? I'm not a very experienced
programmer, how much work would it be to make that change in existing
scripts??
Using a rusty Amiga 4000T, a shiny PowerMac G5, & a homebuilt Ubuntu box
Oxymoron: A thinking liberal.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-users
