All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] shell issues when /bin/sh is 'dash' instead of	'bash'
Date: Thu, 01 Jan 2009 21:43:10 +0100	[thread overview]
Message-ID: <87eizm3ggx.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090101023620.GA13399@cloud.net.au> (Hamish Moffatt's message of "Thu\, 1 Jan 2009 13\:36\:21 +1100")

>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:

 Hamish> 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.

 Hamish> Why aren't we setting SHELL=$(CONFIG_SHELL) somewhere, rather
 Hamish> than using $(CONFIG_SHELL) explicitly in each place? (And why
 Hamish> do I have the feeling we've had this discussion before?)

Because we already discussed it earlier ;) - Without any
conclusion. The CONFIG_SHELL afaik comes from the kconfig legacy, but
other projects like U-Boot have recently skipped it and simply set
SHELL.

I have done it as well for buildroot, and a test build seems to work
fine, so I'll commit it in a moment. We still need to set CONFIG_SHELL
though for the kconfig stuff (or fix their makefiles, but I would
prefer to keep the difference between us and upstream minimal).

 Hamish> Besides is CONFIG_SHELL guaranteed to be bash anyway?

No, it currently falls back to /bin/sh if bash isn't there. We should
probably add a check in dependencies.sh

 Hamish> Happy new year.

You too.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2009-01-01 20:43 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 [this message]
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=87eizm3ggx.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 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.