Re: wrong final bzImage build (regading #14270)

[Arkadiusz Miskiewicz]

On Friday 09 of October 2009, Michael Tokarev wrote:
> Ok, some more to this.
> 
> It turns out dash's built-in echo command interprets \nnn octal
> sequences by default, and there's no way to turn that off.  So,
> for example, sed-zoffset command from arch/x86/boot/Makefile
> (which includes \1 \2 etc substitutions for sed), when echoed
> in verbose mode (V=1), produces.. interesting characters (with
> ascii code 1 and 2).
> 
> It's not practival to replace V=1's echo with /bin/echo I think.
> 
> So I'd say it's not a bug in the build system after all, but
> a bug in dash.  

It's still a bug in build system if you consider that a /bin/sh is a posix 
shell. posix shells don't support \hex notation (see single unix system 
specification).

I had exactly this problem few weeks ago with pdksh as /bin/sh (and 
bugreported to author of that change). As I workaround I used /bin/echo but 
using printf is more sane/portable.

-- 
Arkadiusz MiÅkiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/