All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@googlemail.com>
Cc: paul.eggleton@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] cml1.bbclass: fix kernel menuconfig
Date: Wed, 12 Sep 2012 14:31:50 +0100	[thread overview]
Message-ID: <1347456710.11710.11.camel@ted> (raw)
In-Reply-To: <1347455995-24565-1-git-send-email-schnitzeltony@googlemail.com>

On Wed, 2012-09-12 at 15:19 +0200, Andreas Müller wrote:
> At some host environments the menuconfig displayed wrong characters ang turned
> unusable.
> 
> Similar suggested in [1]
> 
> [1] http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html
> 
> Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
> ---
>  meta/classes/cml1.bbclass |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/meta/classes/cml1.bbclass b/meta/classes/cml1.bbclass
> index 67f17ad..c773684 100644
> --- a/meta/classes/cml1.bbclass
> +++ b/meta/classes/cml1.bbclass
> @@ -9,7 +9,7 @@ addtask configure after do_unpack do_patch before do_compile
>  
>  inherit terminal
>  
> -OE_TERMINAL_EXPORTS += "HOST_EXTRACFLAGS HOSTLDFLAGS HOST_LOADLIBES"
> +OE_TERMINAL_EXPORTS += "HOST_EXTRACFLAGS HOST_LOADLIBES"
>  HOST_EXTRACFLAGS = "${BUILD_CFLAGS} ${BUILD_LDFLAGS}"
>  HOSTLDFLAGS = "${BUILD_LDFLAGS}"
>  HOST_LOADLIBES = "-lncurses"

This effectively just reverts the previous change. The real problem is
that ncurses-native is broken. Could we figure out how/why
ncurses-native is broken and fix the real problem rather than hacking
around it please?

FWIW I've been unable to reproduce this locally :(.

Cheers,

Richard




  reply	other threads:[~2012-09-12 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 13:19 [PATCH] cml1.bbclass: fix kernel menuconfig Andreas Müller
2012-09-12 13:31 ` Richard Purdie [this message]
2012-09-12 13:38   ` Bruce Ashfield
2012-09-12 14:21     ` Samuel Stirtzel
2012-09-12 14:22       ` 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=1347456710.11710.11.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=schnitzeltony@googlemail.com \
    /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.