From: Martin Jansa <martin.jansa@gmail.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 21:46:51 +0200 [thread overview]
Message-ID: <20121023194651.GV3269@jama.jama.net> (raw)
In-Reply-To: <DDDB9E6645DE24488B8485B41A051F471D969119@Mercury.usurf.usu.edu>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
On Tue, Oct 23, 2012 at 07:33:44PM +0000, Jonathan Haws wrote:
> 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.
see this thread
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-June/024199.html
there are some solutions for this (you have to follow it in later months
then 2012-June too).
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-10-23 19:46 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
2012-10-23 19:44 ` Jonathan Haws
2012-10-23 19:46 ` Martin Jansa [this message]
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=20121023194651.GV3269@jama.jama.net \
--to=martin.jansa@gmail.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.