Re: "bitbake -c menuconfig virtual/kernel" fails on ncurses dependency

[Mike Looijmans <mike.looijmans@topic.nl>]

On 11-06-15 07:45, Mike Looijmans wrote:
> On 26-05-15 11:03, Mike Looijmans wrote:
>> On 26-05-15 10:40, Andrea Adami wrote:
>>> On Tue, May 26, 2015 at 10:29 AM, Mike Looijmans
>>> <mike.looijmans@topic.nl> wrote:
>>>> On 26-05-15 10:14, Mike Looijmans wrote:
>>>>>
>>>>> On 26-05-15 09:26, Mike Looijmans wrote:
>>>>>>
>>>>>> On 26-05-15 09:13, Mike Looijmans wrote:
>>>>>>>
>>>>>>> On 26-05-15 09:02, Bruce Ashfield wrote:
>>>>>>>>
>>>>>>>> On Tue, May 26, 2015 at 2:53 AM, Mike Looijmans
>>>>>>>> <mike.looijmans@topic.nl>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I get this when running
>>>>>>>>> bitbake -c menuconfig virtual/kernel
>>>>>>>>>
>>>>>>>>> scripts/kconfig/mconf.o: In function `show_help':
>>>>>>>>> mconf.c:(.text+0x884): undefined reference to `stdscr'
>>>>>>>>> scripts/kconfig/lxdialog/checklist.o: In function `print_arrows':
>>>>>>>>> checklist.c:(.text+0x2c): undefined reference to `wmove'
>>>>>>>>> checklist.c:(.text+0x4c): undefined reference to `acs_map'
>>>>>>>>> checklist.c:(.text+0x54): undefined reference to `waddch'
>>>>>>>>> checklist.c:(.text+0x66): undefined reference to `waddnstr'
>>>>>>>>> checklist.c:(.text+0x76): undefined reference to `wmove'
>>>>>>>>
>>>>>>>>
>>>>>>>> This has popped up on and off for several years now, and we have
>>>>>>>> a few
>>>>>>>> bugzilla
>>>>>>>> entries that track it. The fix is never as simple as we would like.
>>>>>>>>
>>>>>>>> The most recent version is here:
>>>>>>>>
>>>>>>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7609
>>>>>>>>
>>>>>>>> If you have more details about your enviroment, adding them to
>>>>>>>> that bug
>>>>>>>> would
>>>>>>>> be idea.
>>>>>>>>
>>>>>>>> The problem with using the -native version, or the host, is that at
>>>>>>>> times
>>>>>>>> menu
>>>>>>>> config is rendered unusable. The fix isn't only in the
>>>>>>>> dependencies,
>>>>>>>> but in
>>>>>>>> the
>>>>>>>> way that menuconfig is build within the kernel environment.
>>>>>>>>
>>>>>>>> This older bug tracks the details of that:
>>>>>>>>
>>>>>>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=3898
>>>>>>>
>>>>>>>
>>>>>>> I have an Ubuntu 14 system. The weird thing is, that I have several
>>>>>>> almost
>>>>>>> identical machines, and some of them fail and some don't.
>>>>>>>
>>>>>>> This one works fine:
>>>>>>> MACHINE=topic-miami-florida-med-xc7z030
>>>>>>>
>>>>>>> This one fails:
>>>>>>> MACHINE=topic-miami-florida-gen-xc7z030
>>>>>>>
>>>>>>> They all use the same kernel recipe, version, git tag, etc. These
>>>>>>> two
>>>>>>> even
>>>>>>> share the very same defconfig. Their builds run within the same OE
>>>>>>> environment, so the native sysroot for both is the same too!
>>>>>>
>>>>>>
>>>>>> I output "bitbake -c menuconfig virtual/kernel -e" for both
>>>>>> machines into
>>>>>> two
>>>>>> files, then did a find/replace "med" with "gen", and then looked
>>>>>> the the
>>>>>> differences with meld. Both machines use the same environments all
>>>>>> over,
>>>>>> only
>>>>>> differences are time stamps and task checksums.
>>>>>>
>>>>>> Next I'm gonna try the old "remove tmp" trick.
>>>>>
>>> I was there, it will fail (Ubuntu 14.04 fwiw).
>>>
>>>>>
>>>>> Removing tmp did not help either. Forcibly rebuilding ncurses-native
>>>>> also
>>>>> did
>>>>> not help.
>>>
>>> Yes, as strange as it is, you need to bitbake ncurses.
>>
>> Wow, indeed, "bitbake ncurses -c populate_sysroot -f" made the
>> menuconfig work again.
>>
>> Looks like ncurses "fixes" something that ncurses-native broke.
>
> Waaah. I just got this very same problem back, but whatever I try, I
> can't get it to work properly again using the above workaround.

The only horrible hack that got menuconfig working again was to install 
ncurses-dev on the build host.


-- 
Mike Looijmans