All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libtool-cross/native: Force usage of bash due to sstate inconsistencies
Date: Thu, 23 Jan 2014 20:42:57 +0800	[thread overview]
Message-ID: <52E10E51.10701@windriver.com> (raw)
In-Reply-To: <CAP9ODKqTjAESi+B56QFCuKpNJ3fxxmO+_Tx1_gWUxt+VyejycA@mail.gmail.com>



On 01/23/2014 08:37 PM, Otavio Salvador wrote:
> On Thu, Jan 23, 2014 at 10:19 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> Scenario:
>> a) libtool script is built on system with bash as /bin/sh
>> b) machine B installs sstate from build a)
>> c) machine B has dash as /bin/sh
>>
>> In this scenario, the script fails to work properly since its expecting
>> /bin/sh to have bash like syntax and it no longer does have it.
>>
>> This patch forces the configure process to use /bin/bash, not /bin/sh
>> and hence allows the scripts to work correctly when used from sstate.
>>
>> (From OE-Core rev: 2c66aa0fc98b092ebb37baee94e92d1965afd76b)
>>
>> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> Does this work for Fedora, using bash in /usr/bin/bash?
>

Yes, I think so, on Fedora:

$ readlink -f /bin/
/usr/bin


/bin is a symlink which points to /usr/bin.

// Robert


  reply	other threads:[~2014-01-23 12:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 12:19 [PATCH] libtool-cross/native: Force usage of bash due to sstate inconsistencies Richard Purdie
2014-01-23 12:37 ` Otavio Salvador
2014-01-23 12:42   ` Robert Yang [this message]
2014-01-23 12:44     ` Otavio Salvador
2014-01-23 12:48 ` Martin Jansa

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=52E10E51.10701@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.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.