From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: latest updates make kernel menuconfig unusable
Date: Wed, 20 Jun 2012 20:55:51 +0200 [thread overview]
Message-ID: <20120620185551.GU3178@jama.jama.net> (raw)
In-Reply-To: <CALbNGRR1j33mDcTD-q2FD+g2uL1VNZNdDwRX7_MNeUTKtN=ozQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
On Wed, Jun 20, 2012 at 04:20:03PM +0200, Andreas Müller wrote:
> Hi,
>
> since
>
> commit fe417e8a4d625c6933de72163d2fee52ac47f571
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date: Thu May 31 13:22:34 2012 +0000
>
> cmd1.bbclass: Ensure ncurses is built and used for menuconfig tasks
>
> Currently, the task just exits if something goes wrong. This adds the
> ncurses-native dependency. It also adds a small delay before closing the
> window so any messages displayed there can be seen.
>
> Trying to get the kernel build system to correctly find and link with
> our copy of ncurses is some kind of nightmare. I ended up having to add
> it to HOST_LOADLIBES globally for this task which is rather nasty but I
> couldn't find any other way.
>
> [YOCTO #2513]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> my menuconfig is unusable (see screenshot attached). I reverted it and
> can work as before.
>
> I am working on Fedora 15 and set in my local.conf
>
> TERMCMD = "${GNOME_TERMCMD}"
> TERMCMDRUN = "${GNOME_TERMCMDRUN}"
I can confirm the same look&feel with
TERMCMD = "${SCREEN_TERMCMD}"
TERMCMDRUN = "${SCREEN_TERMCMDRUN}"
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-06-20 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 14:20 latest updates make kernel menuconfig unusable Andreas Müller
2012-06-20 18:55 ` Martin Jansa [this message]
2012-06-21 0:29 ` Khem Raj
2012-08-02 11:07 ` Andreas Müller
2012-08-02 14:25 ` Liang Li
2012-09-06 13:30 ` Paul Eggleton
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=20120620185551.GU3178@jama.jama.net \
--to=martin.jansa@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox