From: Marc Ferland <ferlandm@sonatest.com>
To: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Unreadable menuconfig
Date: Tue, 23 Oct 2012 15:41:50 -0400 [thread overview]
Message-ID: <87vce1x9fl.fsf@sonatest.com> (raw)
In-Reply-To: <DDDB9E6645DE24488B8485B41A051F471D96912E@Mercury.usurf.usu.edu> (Jonathan Haws's message of "Tue, 23 Oct 2012 19:34:29 +0000")
Jonathan Haws <Jonathan.Haws@sdl.usu.edu> writes:
> When I run 'bitbake linux-yocto -c menuconfig' I was not getting a
> menuconfig - I had to tell my local.conf to use screen because auto
> was selecting a gnome terminal which would resize itself to something
> too small and menuconfig would exit with an error.
>
> Now I can get menuconfig and make changes, but it is extremely
> difficult to read. I have attached a screenshot of what I am talking
> about.
>
> Can anyone point me in the right direction on how to fix this? I
> would like to use the correct commands so that I don't mess anything
> up. Right now I have resorted to running menuconfig down in my build
> directory where the .config file is stored with the kernel source.
>
> Thoughts?
>
Try:
OE_TERMINAL = "xterm"
in your local.conf
Marc
next prev parent reply other threads:[~2012-10-23 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 19:33 Unreadable menuconfig Jonathan Haws
2012-10-23 19:34 ` Jonathan Haws
2012-10-23 19:41 ` Marc Ferland [this message]
2012-10-23 19:44 ` Jonathan Haws
2012-10-23 19:46 ` Martin Jansa
2012-10-23 19:54 ` Jonathan Haws
2012-10-23 20:04 ` Martin Jansa
2012-10-23 20:08 ` Jonathan Haws
2012-10-23 20:13 ` 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=87vce1x9fl.fsf@sonatest.com \
--to=ferlandm@sonatest.com \
--cc=Jonathan.Haws@sdl.usu.edu \
--cc=yocto@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.