Unreadable menuconfig

Unreadable menuconfig

[Jonathan Haws]

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?

Thanks!
Jonathan

Re: Unreadable menuconfig

[Jonathan Haws]

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

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?

Thanks!
Jonathan


PS -- HERE IS THE ATTACHMENT...

[-- Attachment #2: snapshot.png --]
[-- Type: image/png, Size: 113651 bytes --]

Re: Unreadable menuconfig

[Marc Ferland]

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

Re: Unreadable menuconfig

[Jonathan Haws]

>Try:
>
>OE_TERMINAL = "xterm"
>
>in your local.conf

I get the exact same thing, just in xterm instead of konsole.

Re: Unreadable menuconfig

[Martin Jansa]

[-- 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 --]

Re: Unreadable menuconfig

[Jonathan Haws]

Thanks for the help.  I used the solution from the following thread to take care of it:

http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html

Are there others having this issue?  If so, is it something that should be pushed upstream?

Thanks!

Re: Unreadable menuconfig

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

On Tue, Oct 23, 2012 at 07:54:58PM +0000, Jonathan Haws wrote:
> Thanks for the help.  I used the solution from the following thread to take care of it:
> 
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-August/027130.html
> 
> Are there others having this issue?  If so, is it something that should be pushed upstream?

It's still valid for me, I'm still using this
https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626

Cheers,
-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: Unreadable menuconfig

[Jonathan Haws]

>It's still valid for me, I'm still using this
>https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626

Hmmmm.  I did a fresh download of the Yocto repos last week and that is not what I have.  My file still has the HOSTLDFLAGS variable set.

Re: Unreadable menuconfig

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

On Tue, Oct 23, 2012 at 08:08:29PM +0000, Jonathan Haws wrote:
> >It's still valid for me, I'm still using this
> >https://github.com/shr-distribution/oe-core/commit/5d5e8783c0db7e2f0488eea02f795c9f543cd626
> 
> Hmmmm.  I did a fresh download of the Yocto repos last week and that is not what I have.  My file still has the HOSTLDFLAGS variable set.

this isn't in upstream oe-core repo, but in shr branch for
shr-distribution.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]