[meta-freescale] Yocto 1.8 menuconfig does not show up

[Seifert, Thomas (T.)]

Hello Daiane,

thank you for you answer! 

to your question: When you say nothing, what do you mean? No error, no warning, no log at all?

Yes there is nothing. I start the command and the terminal does not come back and nothing does happen.


I can start menuconfig  with "make menuconfig"  in the kernel code folder. But it is not configured .

Do you suggest to use stable yocto fido 1.8?

Mit freundlichen Grüßen / with best regards
----------------------------------------------------------
Thomas Seifert
Lead Software Engineer
Visteon Inovation and Technology GmbH
Visteonstrasse 4-10
50170 Kerpen
Germany



-----Original Message-----
From: angolini at gmail.com [mailto:angolini at gmail.com] On Behalf Of Daiane Angolini
Sent: Dienstag, 16. Juni 2015 12:59
To: Seifert, Thomas (T.)
Cc: meta-freescale at yoctoproject.org
Subject: Re: [meta-freescale] Yocto 1.8 menuconfig does not show up

On Tue, Jun 16, 2015 at 3:36 AM, Seifert, Thomas (T.) <tbruenck at visteon.com> wrote:
>
> Hello Wandboard Community,
>
> My setup:
>
> HW: Wandboard Quad + HDMI Touchscreen
> SW: Yocto 1.8 https://github.com/Freescale/fsl-community-bsp-platform 
> -b master -> build on VirtualBox Ububuntu 15.04


Yocto 1.8 is not -b master

In master, we are today developing 1.9. 1.8 is fido http://freescale.github.io/doc/release-notes/1.8/

>
> I can build a core-image-x11 on Ubuntu and run it on my hardware. That is good!
>
> Now I want to activate USB touchscreen support in the kernel. BUT: bitbake linux-wandboard -c menuconfig leads to nothing :  no menuconfig menu does show up.
>

When you say nothing, what do you mean? No error, no warning, no log at all?

>
> I can start menuconfig direct in ~/fsl-community-bsp/build/tmp/work/wandboard_quad-poky-linux-gnueabi/linux-wandboard/3.10.53-r0/git with "make menuconfig" but it has all default values in.
>
> Has somebody experienced the same? And can help me?

I remember a long time ago I faced a similar problem and it was due to remote server. It was caused somehow by ncurses. There was a variable used to configure which program to use on remote server to display the menuconfig window. But I don't remember more than that, sorry.

Daiane
>
>
>
> Mit freundlichen Grüßen / with best regards
> ----------------------------------------------------------
>
> Thomas Seifert
>
> Lead Software Engineer
>
> Visteon Inovation and Technology GmbH
>
> Visteonstrasse 4-10
>
> 50170 Kerpen
>
> Germany
>
>
>
>
>
>
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
>