All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] kernel: fix menuconfig
Date: Thu, 03 Mar 2011 11:12:51 -0800	[thread overview]
Message-ID: <4D6FE833.8090805@intel.com> (raw)
In-Reply-To: <cover.1299014724.git.bruce.ashfield@windriver.com>

On 03/01/2011 01:28 PM, Bruce Ashfield wrote:
> Fixes [BUGID #598]
>
> The explicit addition of "bash" before "make menuconfig"
> is clearing variables that are required for pseudo. The
> end result is that menuconfig often fails silently with:
>
> ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored.
>
> Removing bash from the menuconfig SHELLCMDS variable fixes
> the pseudo problem.
>
> As near as I can tell this is unversally safe (i.e. with
> a different TERMCMD), but I'm willing to be correct and/or
> replaced by a better patch. But this definitely fixed the
> problem for me.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
>    Branch: zedd/kernel
>    Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Thanks,
>      Bruce Ashfield<bruce.ashfield@windriver.com>
> ---
>
>
> Bruce Ashfield (1):
>    kernel: remove explicit bash call in do_menuconfig
>
>   meta/classes/kernel.bbclass |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Merged into Bernard, OE-Core and Master

Thanks
	Sau!


      parent reply	other threads:[~2011-03-03 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-01 21:28 [PATCH 0/1] kernel: fix menuconfig Bruce Ashfield
2011-03-01 21:28 ` [PATCH 1/1] kernel: remove explicit bash call in do_menuconfig Bruce Ashfield
2011-03-03 19:12 ` Saul Wold [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=4D6FE833.8090805@intel.com \
    --to=saul.wold@intel.com \
    --cc=poky@yoctoproject.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.