From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] shell issues when /bin/sh is 'dash' instead of 'bash'
Date: Thu, 1 Jan 2009 13:36:21 +1100 [thread overview]
Message-ID: <20090101023620.GA13399@cloud.net.au> (raw)
In-Reply-To: <bbbeeccd0812311504p2e7f96a6l923c938acac8acf0@mail.gmail.com>
On Wed, Dec 31, 2008 at 04:04:37PM -0700, Wade Berrier wrote:
> The result is that some files don't get installed into the target
> system when /bin/sh points to dash (like on recent ubuntu and debian?
> distros)
>
> Attached is a patch to use CONFIG_SHELL.
Why aren't we setting SHELL=$(CONFIG_SHELL) somewhere, rather than using
$(CONFIG_SHELL) explicitly in each place? (And why do I have the feeling
we've had this discussion before?)
> Question: is this the best way to fix this? Or maybe these packages
> should be fixed more in the style of how Jacmet fixed grep? (see
> http://sources.uclibc.org/index.py/trunk/buildroot/package/grep/grep.mk?r1=22930&r2=22931
> )
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.
Besides is CONFIG_SHELL guaranteed to be bash anyway?
Happy new year.
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next prev parent reply other threads:[~2009-01-01 2:36 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 [this message]
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
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=20090101023620.GA13399@cloud.net.au \
--to=hamish@cloud.net.au \
--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 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.