From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] shell issues when /bin/sh is 'dash' instead of 'bash'
Date: Mon, 05 Jan 2009 09:53:39 +0100 [thread overview]
Message-ID: <87aba6yvzg.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <alpine.LFD.2.00.0901041650200.26118@xanadu.home> (Nicolas Pitre's message of "Sun\, 04 Jan 2009 16\:53\:41 -0500 \(EST\)")
>>>>> "Nicolas" == Nicolas Pitre <nico@cam.org> writes:
Hi,
>> dash(1) on my system says -ot is supported anyway. If not perhaps it can
>> be expressed in a better way; I think that would be better than this
>> fix.
Nicolas> There are other places where brace expansion is used for arguments to
Nicolas> patch-kernel.sh, and dash doesn't supports that. You end up with a
Nicolas> kernel missing appropriate patches, etc.
Exactly. The best way forward is imho to always use bash like what
current svn is doing.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-01-05 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 23:04 [Buildroot] shell issues when /bin/sh is 'dash' instead of 'bash' Wade Berrier
2009-01-01 2:36 ` Hamish Moffatt
2009-01-01 14:40 ` Wade Berrier
2009-01-01 20:43 ` Peter Korsgaard
2009-01-04 21:53 ` Nicolas Pitre
2009-01-05 8:53 ` Peter Korsgaard [this message]
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=87aba6yvzg.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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