Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 19 May 2015 13:43:26 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] Build process uses script to add CFI directives
 to x86 asm

* u-wsnj@...ey.se <u-wsnj@...ey.se> [2015-05-19 13:16:22 +0200]:
> 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.
> 

configure already uses its own echo definition

so ash's echo should not be used

how did the config script end up calling ash's echo?

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.