From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Cyrill Gorcunov <gorcunov@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: wrong final bzImage build (regading #14270)
Date: Fri, 9 Oct 2009 22:02:51 +0200 [thread overview]
Message-ID: <200910092202.51208.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <4ACF9184.9040104@msgid.tls.msk.ru>
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/
WARNING: multiple messages have this Message-ID (diff)
From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Cyrill Gorcunov <gorcunov@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: wrong final bzImage build (regading #14270)
Date: Fri, 9 Oct 2009 22:02:51 +0200 [thread overview]
Message-ID: <200910092202.51208.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <4ACF9184.9040104@msgid.tls.msk.ru>
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/
next prev parent reply other threads:[~2009-10-09 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 14:17 wrong final bzImage build (regading #14270) Michael Tokarev
2009-10-09 14:26 ` Michael Tokarev
2009-10-09 14:58 ` Cyrill Gorcunov
2009-10-09 17:03 ` H. Peter Anvin
2009-10-09 17:03 ` H. Peter Anvin
[not found] ` <4ACF6CF8.4060204-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-10-09 17:14 ` Michael Tokarev
2009-10-09 17:14 ` Michael Tokarev
2009-10-09 19:39 ` Michael Tokarev
[not found] ` <4ACF9184.9040104-Gdu+ltImwkhes2APU0mLOQ@public.gmane.org>
2009-10-09 19:59 ` Cyrill Gorcunov
2009-10-09 19:59 ` Cyrill Gorcunov
2009-10-09 20:02 ` Arkadiusz Miskiewicz [this message]
2009-10-09 20:02 ` Arkadiusz Miskiewicz
2009-10-09 20:56 ` H. Peter Anvin
[not found] ` <4ACFA36F.6000105-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2009-10-09 21:27 ` Michael Tokarev
2009-10-09 21:27 ` Michael Tokarev
2009-10-09 21:29 ` H. Peter Anvin
2009-10-09 20:05 ` Michael Tokarev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200910092202.51208.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=gorcunov@gmail.com \
--cc=hpa@zytor.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=rjw@sisk.pl \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.