All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] bash: make job control really work
Date: Tue, 01 Nov 2011 10:21:08 +0000	[thread overview]
Message-ID: <1320142868.13918.0.camel@ted> (raw)
In-Reply-To: <ac7b821f266e932e267a4d62af83586ba3261a98.1320134607.git.dexuan.cui@intel.com>

On Tue, 2011-11-01 at 16:05 +0800, Dexuan Cui wrote:
> It turns out 9393ff833f44570fd5f500bc9de6c72db94b0296 didn't really fix
> the bug.
> 
> This patch is made and tested after I read the link below
> http://www.mail-archive.com/bug-bash@gnu.org/msg03107.html
> 
> [YOCTO #487]
> 
> Signed-off-by: Dexuan Cui <dexuan.cui@intel.com>
> ---
>  meta/recipes-extended/bash/bash.inc    |    1 +
>  meta/recipes-extended/bash/bash_4.2.bb |    2 +-
>  2 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/meta/recipes-extended/bash/bash.inc b/meta/recipes-extended/bash/bash.inc
> index d55e517..d495538 100644
> --- a/meta/recipes-extended/bash/bash.inc
> +++ b/meta/recipes-extended/bash/bash.inc
> @@ -23,6 +23,7 @@ ALTERNATIVE_LINK = "${base_bindir}/sh"
>  ALTERNATIVE_PRIORITY = "100"
>  
>  do_configure () {
> +	export bash_cv_job_control_missing=present
>  	gnu-configize
>  	oe_runconf
>  }

This really should go into the common site files...

Cheers,

Richard





  reply	other threads:[~2011-11-01 10:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01  8:05 [PATCH 0/1] fix bug 487 Dexuan Cui
2011-11-01  8:05 ` [PATCH 1/1] bash: make job control really work Dexuan Cui
2011-11-01 10:21   ` Richard Purdie [this message]
2011-11-02  7:10     ` Cui, Dexuan
2011-11-02 10:35       ` Richard Purdie
2011-11-02 11:41         ` [PATCH] bash: Ensure we fully reautoconf the recipes so site data is used Richard Purdie
2011-11-02 15:48         ` [PATCH 1/1] bash: make job control really work Cui, Dexuan

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=1320142868.13918.0.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.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.