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

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

[Mike Looijmans]

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'

A bit of googling reveals that this is probably due to "ncurses" not being 
present.

I just can't figure out what the proper syntax for this dependency would be. 
menuconfig needs the "native" version, so it's not simply DEPENDS+=ncurses here.


Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Robert Yang]

On 05/26/2015 02:53 PM, Mike Looijmans 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'
>
> A bit of googling reveals that this is probably due to "ncurses" not being present.
>
> I just can't figure out what the proper syntax for this dependency would be.
> menuconfig needs the "native" version, so it's not simply DEPENDS+=ncurses here.
>

Try:
DEPENDS += "ncurses-native" ?

// Robert


>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Embedded Products
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> Telefax: +31 (0) 499 33 69 70
> E-mail: mike.looijmans@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>

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

[Bruce Ashfield]

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

Cheers,

Bruce

>
> A bit of googling reveals that this is probably due to "ncurses" not being
> present.
>
> I just can't figure out what the proper syntax for this dependency would be.
> menuconfig needs the "native" version, so it's not simply DEPENDS+=ncurses
> here.
>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Embedded Products
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> Telefax: +31 (0) 499 33 69 70
> E-mail: mike.looijmans@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

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

[Mike Looijmans]

On 26-05-15 08:53, Mike Looijmans 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'
>
> A bit of googling reveals that this is probably due to "ncurses" not being
> present.
>
> I just can't figure out what the proper syntax for this dependency would be.
> menuconfig needs the "native" version, so it's not simply DEPENDS+=ncurses here.

Hmm strange, "kernel.bbclass" inherits "cml1.bbclass", which already states:
do_menuconfig[depends] += "ncurses-native:do_populate_sysroot"

And ncurses-native has indeed been built. But menuconfig still fails to link.



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Mike Looijmans]

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!


Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Mike Looijmans]

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.



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Mike Looijmans]

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.

Removing tmp did not help either. Forcibly rebuilding ncurses-native also did 
not help.

I'm now trying a complete clean start with current master branches...



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Mike Looijmans]

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.
>
> Removing tmp did not help either. Forcibly rebuilding ncurses-native also did
> not help.
>
> I'm now trying a complete clean start with current master branches...

Okay, that made things consistent again. Now all machines fail.




Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Andrea Adami]

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.

>>
>> I'm now trying a complete clean start with current master branches...
>
>
> Okay, that made things consistent again. Now all machines fail.
>

This little bug is very nasty and I've always postponed a deeper
analysis because of other evil issues with the linux kernel taking all
my little time :).


Cheers
Andrea

>
>
>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Embedded Products
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> Telefax: +31 (0) 499 33 69 70
> E-mail: mike.looijmans@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

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

[Mike Looijmans]

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.


>>> I'm now trying a complete clean start with current master branches...
>>
>>
>> Okay, that made things consistent again. Now all machines fail.
>>
>
> This little bug is very nasty and I've always postponed a deeper
> analysis because of other evil issues with the linux kernel taking all
> my little time :).

Ah well, never a boring day :)



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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

[Mike Looijmans]

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.



-- 
Mike Looijmans

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

[Mike Looijmans]

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

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

[Andrea Adami]

On Thu, Jun 11, 2015 at 7:57 AM, Mike Looijmans <mike.looijmans@topic.nl> wrote:
> 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

I see the common point here is Ubuntu 14.x.
This never happens on my old Gentoo buildhost, where you don't have
the split with -dev packages.

Neverthless, reading the comments in the Yocto bugzilla it looks like
the kernel could be the culprit.
I'll try to debug that once 4.1 is out.

Cheers

Andrea