Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: "bitbake -c menuconfig virtual/kernel" fails on ncurses dependency
Date: Tue, 26 May 2015 10:29:47 +0200	[thread overview]
Message-ID: <55642EFB.4070102@topic.nl> (raw)
In-Reply-To: <55642B75.8050909@topic.nl>

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







  reply	other threads:[~2015-05-26  8:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-26  6:53 "bitbake -c menuconfig virtual/kernel" fails on ncurses dependency Mike Looijmans
2015-05-26  7:01 ` Robert Yang
2015-05-26  7:02 ` Bruce Ashfield
2015-05-26  7:13   ` Mike Looijmans
2015-05-26  7:26     ` Mike Looijmans
2015-05-26  8:14       ` Mike Looijmans
2015-05-26  8:29         ` Mike Looijmans [this message]
2015-05-26  8:40           ` Andrea Adami
2015-05-26  9:03             ` Mike Looijmans
2015-06-11  5:45               ` Mike Looijmans
2015-06-11  5:57                 ` Mike Looijmans
2015-06-11  7:50                   ` Andrea Adami
2015-05-26  7:03 ` Mike Looijmans

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=55642EFB.4070102@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox