From: Arnd Hannemann <arnd@arndnet.de>
To: SL Baur <steve@xemacs.org>
Cc: Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de>,
Sam Ravnborg <sam@ravnborg.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Timur Tabi <timur@freescale.com>,
Tony Breeds <tony@bakeyournoodle.com>,
linux-kernel@vger.kernel.org
Subject: Re: cross-compiling on OS X, make menuconfig fails
Date: Mon, 12 May 2008 15:22:17 +0200 [thread overview]
Message-ID: <48284489.4040609@arndnet.de> (raw)
In-Reply-To: <ed10ee420805030234o39141933v8c26d7895ed3f9a@mail.gmail.com>
SL Baur wrote:
> On 5/3/08, Roland Kuhn <rkuhn@e18.physik.tu-muenchen.de> wrote:
>
>> Hi Steve!
>>
>>
>> On 3 May 2008, at 08:55, SL Baur wrote:
>>
>
>
>>> $ uname -v
>>> Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007;
>>> root:xnu792.25.20~1/RELEASE_I386
>>>
>>>
>>>
>> Yes, they changed that between Tiger and Leopard, where I have
>>
>> ---
>> $ uname -v
>> Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008;
>> root:xnu-1228.4.31~1/RELEASE_I386
>> $ /bin/bash -c 'echo -e "buh\n"'
>> buh
>>
>> $ /bin/sh -c 'echo -e "buh\n"'
>> -e buh
>>
>> $ /bin/echo -e "buh\n"
>> -e buh\n
>> ---
>>
>> The second one is POSIX+XSI, the third one plain POSIX. The first one is
>> what people are used to ;-)
>>
>
> Check.
>
> $ /bin/bash -c 'echo -e "buh\n"'
> buh
>
> $ /bin/sh -c 'echo -e "buh\n"'
> buh
>
> $ /bin/echo -e "buh\n"
> -e buh\n
>
> Of all the things to "standardize" on, why something like bash
> which has no standards? pdksh, ash, dash or POSIX mode zsh,
> would have been better...
>
>
It also depends on the shell option xpg_echo IIRC.
If xpg_echo is off echo -e should work in /bin/sh, too.
Regards,
Arnd
next prev parent reply other threads:[~2008-05-12 13:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 1:34 cross-compiling on OS X, make menuconfig fails timur
2008-04-28 1:51 ` Tony Breeds
2008-04-29 15:07 ` Timur Tabi
2008-04-29 16:45 ` Sam Ravnborg
2008-04-29 17:20 ` Al Viro
2008-04-29 18:06 ` Sam Ravnborg
2008-04-30 13:54 ` Timur Tabi
2008-04-30 14:18 ` Sam Ravnborg
2008-05-03 6:55 ` SL Baur
2008-05-03 8:01 ` Sam Ravnborg
2008-05-03 8:40 ` Roland Kuhn
2008-05-03 9:34 ` SL Baur
2008-05-12 13:22 ` Arnd Hannemann [this message]
2008-04-28 18:46 ` Roland Kuhn
2008-04-29 14:51 ` Timur Tabi
2008-04-29 16:45 ` Sam Ravnborg
2008-04-29 16:48 ` Al Viro
2008-04-29 20:27 ` Why use /bin/sh in kernel build system? Mark Rustad
2008-04-29 21:41 ` Alexey Dobriyan
2008-04-29 22:24 ` Willy Tarreau
2008-04-29 22:40 ` Timur Tabi
2008-04-30 9:42 ` SL Baur
2008-04-30 11:48 ` Jan Engelhardt
2008-04-29 22:46 ` cross-compiling on OS X, make menuconfig fails Bernd Petrovitsch
-- strict thread matches above, loose matches on Subject: below --
2008-04-28 1:34 Timur Tabi
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=48284489.4040609@arndnet.de \
--to=arnd@arndnet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rkuhn@e18.physik.tu-muenchen.de \
--cc=sam@ravnborg.org \
--cc=steve@xemacs.org \
--cc=timur@freescale.com \
--cc=tony@bakeyournoodle.com \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox