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

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: [email protected]
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

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: [email protected]
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

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.

Quoted 11 lines · 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'

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

Quoted 24 lines · Bruce Ashfield

Quoted 11 lines · 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'

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.

Quoted 7 lines

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!

Quoted 41 lines · Mike Looijmans

Quoted 25 lines · Bruce Ashfield

Quoted 11 lines · 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'

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.

Quoted 8 lines

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

Quoted 6 lines

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.

Quoted 55 lines · Mike Looijmans

Quoted 42 lines · Mike Looijmans

Quoted 31 lines · Bruce Ashfield

Quoted 11 lines · 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'

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.

Quoted 3 lines

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

Quoted 6 lines

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.

Quoted 1 line

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...

Quoted 72 lines · Mike Looijmans

Quoted 70 lines · Mike Looijmans

Quoted 52 lines · Mike Looijmans

Quoted 38 lines · Bruce Ashfield

Quoted 4 lines · Mike Looijmans

I get this when running
bitbake -c menuconfig virtual/kernel

Quoted 8 lines

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.

Quoted 3 lines

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

Quoted 7 lines

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.

Quoted 2 lines

Quoted 1 line

Next I'm gonna try the old "remove tmp" trick.

Quoted 4 lines

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

Quoted 2 lines

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: [email protected]
Website: www.topicproducts.com

Please consider the environment before printing this e-mail

--
_______________________________________________
Openembedded-core mailing list [email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Quoted 73 lines · Mike Looijmans

Quoted 72 lines · Mike Looijmans

Quoted 70 lines · Mike Looijmans

Quoted 52 lines · Mike Looijmans

Quoted 38 lines · Bruce Ashfield

Quoted 4 lines · Mike Looijmans

I get this when running
bitbake -c menuconfig virtual/kernel

Quoted 8 lines

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.

Quoted 3 lines

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

Quoted 7 lines

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.

Quoted 2 lines

Quoted 2 lines

Quoted 1 line

Next I'm gonna try the old "remove tmp" trick.

I was there, it will fail (Ubuntu 14.04 fwiw).

Quoted 4 lines

Quoted 4 lines

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.

Quoted 5 lines

Quoted 1 line

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 :).

Quoted 90 lines · Andrea Adami

Quoted 78 lines · Mike Looijmans

Quoted 77 lines · Mike Looijmans

Quoted 75 lines · Mike Looijmans

Quoted 54 lines · Mike Looijmans

Quoted 40 lines · Bruce Ashfield

Quoted 4 lines · Mike Looijmans

I get this when running
bitbake -c menuconfig virtual/kernel

Quoted 8 lines

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.

Quoted 3 lines

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

Quoted 7 lines

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.

Quoted 2 lines

Quoted 2 lines

Quoted 1 line

Next I'm gonna try the old "remove tmp" trick.

I was there, it will fail (Ubuntu 14.04 fwiw).

Quoted 5 lines

Quoted 5 lines

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

Quoted 1 line

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.

Quoted 95 lines · Mike Looijmans

Quoted 93 lines · Andrea Adami

Quoted 80 lines · Mike Looijmans

Quoted 79 lines · Mike Looijmans

Quoted 77 lines · Mike Looijmans

Quoted 55 lines · Mike Looijmans

Quoted 41 lines · Bruce Ashfield

Quoted 4 lines · Mike Looijmans

I get this when running
bitbake -c menuconfig virtual/kernel

Quoted 8 lines

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.

Quoted 3 lines

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

Quoted 8 lines

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.

Quoted 2 lines

Quoted 2 lines

Quoted 1 line

Next I'm gonna try the old "remove tmp" trick.

I was there, it will fail (Ubuntu 14.04 fwiw).

Quoted 5 lines

Quoted 5 lines

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.

Quoted 4 lines

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.

Quoted 111 lines · Mike Looijmans

Quoted 109 lines · Mike Looijmans

Quoted 105 lines · Andrea Adami

Quoted 89 lines · Mike Looijmans

Quoted 87 lines · Mike Looijmans

Quoted 84 lines · Mike Looijmans

Quoted 60 lines · Mike Looijmans

Quoted 44 lines · Bruce Ashfield

Quoted 5 lines · Mike Looijmans

I get this when running
bitbake -c menuconfig virtual/kernel

Quoted 8 lines

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.

Quoted 3 lines

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

Quoted 8 lines

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.

Quoted 3 lines

Quoted 3 lines

Quoted 1 line

Next I'm gonna try the old "remove tmp" trick.

I was there, it will fail (Ubuntu 14.04 fwiw).

Quoted 5 lines

Quoted 5 lines

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.

Quoted 8 lines

Quoted 4 lines

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