Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519111622.GF8197@example.net>
Date: Tue, 19 May 2015 13:16:22 +0200
From: u-wsnj@...ey.se
To: musl@...ts.openwall.com
Subject: Re: [PATCH] Build process uses script to add CFI directives
 to x86 asm

On Tue, May 19, 2015 at 11:31:14AM +0200, Alex Dowad wrote:
> awk code with not a word of complaint. The only trouble was with the use of "echo"
> in the configure script -- BusyBox ash's "echo" is different from bash's.

Indeed, portable sh scripts should be using printf instead of echo,
every time.

echo(){ printf '%s\n' "$@"; }

yields a well-behaving "plain" echo variant.

If one needs some special tricks, printf covers more cases than echo anyway.

I may be wrong but I am not aware of a "nowadays practically useful"
platform where printf is not available (even if we do not consider a
possibility to make it available).

Rune

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.