bitbake menuconfig fails

bitbake menuconfig fails

[Mircea Gliga]

Hello

We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb)- 
everything ok.
I'm trying to upgrade to 4.14, I created a new recipe 
linux-stable_4.14.bb. They live side by side, for now.
But with the 4.14 kernel when running `bitbake -c menuconfig 
linux-stable`, the new terminal comes up and I get the following error:

   HOSTCC  scripts/basic/fixdep
   GEN     ./Makefile
   HOSTCC  scripts/kconfig/mconf.o
   HOSTCC  scripts/kconfig/zconf.tab.o
   HOSTCC  scripts/kconfig/lxdialog/checklist.o
   HOSTCC  scripts/kconfig/lxdialog/util.o
   HOSTCC  scripts/kconfig/lxdialog/inputbox.o
   HOSTCC  scripts/kconfig/lxdialog/textbox.o
   HOSTCC  scripts/kconfig/lxdialog/yesno.o
   HOSTCC  scripts/kconfig/lxdialog/menubox.o
   HOSTLD  scripts/kconfig/mconf
/usr/bin/ld: cannot find -lncursesw
collect2: error: ld returned 1 exit status
scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf' failed
make[3]: *** [scripts/kconfig/mconf] Error 1
/media/mircea/ExtLinux/Adventure/testBuildServer/product-sama5-kernel/yocto/build/tmp/work-shared/cuxe/kernel-source/Makefile:548: 
recipe for target 'menuconfig' failed
make[2]: *** [menuconfig] Error 2
Makefile:146: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
Makefile:24: recipe for target '__sub-make' failed
make: *** [__sub-make] Error 2
Command failed.


If I rename linux-stable_4.14.bb to linux-stable_4.14.bb___, then run 
bitbake again (now the build system is working with the 4.8 kernel 
again) => menuconfig starts and works as expected.

I'm using krogoth, 2.1.2, Debian 8 (jessie)

I also tried to config the kernel outside of yocto, downloaded 
https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.4.tar.xz, 
extracted and run make menuconfig => works as expected

Any hints are appreciated.

Thanks

Re: bitbake menuconfig fails

[Zoran Stojsavljevic]

[-- Attachment #1: Type: text/plain, Size: 2906 bytes --]

Hello Mircea,

From my point of view:

*> /usr/bin/ld: cannot find -lncursesw*
> collect2: error: ld returned 1 exit status
> scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf'
failed

The first line explains it all. You could not configure 4.14, since for
this you should have ncurses package. I would further say, the
YOCTO ncurses version you have, which is used for 4.8 is outdated, so you
need newer (matching) YOCTO version for 4.14.

Why you are able to configure 4.14 outside of yocto? Because you use
another version of ncurses, one which is host native to
Debian 8. YOCTO probably uses some other host based ncurses inside YOCTO
(in Open Embedded/meta layer, my best guess).

Zoran

On Wed, Dec 6, 2017 at 7:31 AM, Mircea Gliga <mircea.gliga@vitheia.com>
wrote:

> Hello
>
> We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb)-
> everything ok.
> I'm trying to upgrade to 4.14, I created a new recipe linux-stable_4.14.bb.
> They live side by side, for now.
> But with the 4.14 kernel when running `bitbake -c menuconfig
> linux-stable`, the new terminal comes up and I get the following error:
>
>   HOSTCC  scripts/basic/fixdep
>   GEN     ./Makefile
>   HOSTCC  scripts/kconfig/mconf.o
>   HOSTCC  scripts/kconfig/zconf.tab.o
>   HOSTCC  scripts/kconfig/lxdialog/checklist.o
>   HOSTCC  scripts/kconfig/lxdialog/util.o
>   HOSTCC  scripts/kconfig/lxdialog/inputbox.o
>   HOSTCC  scripts/kconfig/lxdialog/textbox.o
>   HOSTCC  scripts/kconfig/lxdialog/yesno.o
>   HOSTCC  scripts/kconfig/lxdialog/menubox.o
>   HOSTLD  scripts/kconfig/mconf
> /usr/bin/ld: cannot find -lncursesw
> collect2: error: ld returned 1 exit status
> scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf' failed
> make[3]: *** [scripts/kconfig/mconf] Error 1
> /media/mircea/ExtLinux/Adventure/testBuildServer/product-
> sama5-kernel/yocto/build/tmp/work-shared/cuxe/kernel-source/Makefile:548:
> recipe for target 'menuconfig' failed
> make[2]: *** [menuconfig] Error 2
> Makefile:146: recipe for target 'sub-make' failed
> make[1]: *** [sub-make] Error 2
> Makefile:24: recipe for target '__sub-make' failed
> make: *** [__sub-make] Error 2
> Command failed.
>
>
> If I rename linux-stable_4.14.bb to linux-stable_4.14.bb___, then run
> bitbake again (now the build system is working with the 4.8 kernel again)
> => menuconfig starts and works as expected.
>
> I'm using krogoth, 2.1.2, Debian 8 (jessie)
>
> I also tried to config the kernel outside of yocto, downloaded
> https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.4.tar.xz,
> extracted and run make menuconfig => works as expected
>
> Any hints are appreciated.
>
> Thanks
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

[-- Attachment #2: Type: text/html, Size: 4549 bytes --]

Re: bitbake menuconfig fails

[Mircea Gliga]

[-- Attachment #1: Type: text/plain, Size: 3706 bytes --]

Thanks Zoran
What you say makes perfect sense.
I also got the feeling that something doesn't match between the new 
kernel and yocto.
Maybe I should also upgrade yocto.

Thanks again.

On 06/12/17 09:22, Zoran Stojsavljevic wrote:
> Hello Mircea,
>
> From my point of view:
>
> /_> /usr/bin/ld: cannot find -lncursesw_/
> > collect2: error: ld returned 1 exit status
> > scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf' failed
>
> The first line explains it all. You could not configure 4.14, since 
> for this you should have ncurses package. I would further say, the
> YOCTO ncurses version you have, which is used for 4.8 is outdated, so 
> you need newer (matching) YOCTO version for 4.14.
>
> Why you are able to configure 4.14 outside of yocto? Because you use 
> another version of ncurses, one which is host native to
> Debian 8. YOCTO probably uses some other host based ncurses inside 
> YOCTO (in Open Embedded/meta layer, my best guess).
>
> Zoran
>
> On Wed, Dec 6, 2017 at 7:31 AM, Mircea Gliga <mircea.gliga@vitheia.com 
> <mailto:mircea.gliga@vitheia.com>> wrote:
>
>     Hello
>
>     We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb
>     <http://linux-stable_4.8.bb>)- everything ok.
>     I'm trying to upgrade to 4.14, I created a new recipe
>     linux-stable_4.14.bb <http://linux-stable_4.14.bb>. They live side
>     by side, for now.
>     But with the 4.14 kernel when running `bitbake -c menuconfig
>     linux-stable`, the new terminal comes up and I get the following
>     error:
>
>       HOSTCC  scripts/basic/fixdep
>       GEN     ./Makefile
>       HOSTCC  scripts/kconfig/mconf.o
>       HOSTCC  scripts/kconfig/zconf.tab.o
>       HOSTCC  scripts/kconfig/lxdialog/checklist.o
>       HOSTCC  scripts/kconfig/lxdialog/util.o
>       HOSTCC  scripts/kconfig/lxdialog/inputbox.o
>       HOSTCC  scripts/kconfig/lxdialog/textbox.o
>       HOSTCC  scripts/kconfig/lxdialog/yesno.o
>       HOSTCC  scripts/kconfig/lxdialog/menubox.o
>       HOSTLD  scripts/kconfig/mconf
>     /usr/bin/ld: cannot find -lncursesw
>     collect2: error: ld returned 1 exit status
>     scripts/Makefile.host:111: recipe for target
>     'scripts/kconfig/mconf' failed
>     make[3]: *** [scripts/kconfig/mconf] Error 1
>     /media/mircea/ExtLinux/Adventure/testBuildServer/product-sama5-kernel/yocto/build/tmp/work-shared/cuxe/kernel-source/Makefile:548:
>     recipe for target 'menuconfig' failed
>     make[2]: *** [menuconfig] Error 2
>     Makefile:146: recipe for target 'sub-make' failed
>     make[1]: *** [sub-make] Error 2
>     Makefile:24: recipe for target '__sub-make' failed
>     make: *** [__sub-make] Error 2
>     Command failed.
>
>
>     If I rename linux-stable_4.14.bb <http://linux-stable_4.14.bb> to
>     linux-stable_4.14.bb___, then run bitbake again (now the build
>     system is working with the 4.8 kernel again) => menuconfig starts
>     and works as expected.
>
>     I'm using krogoth, 2.1.2, Debian 8 (jessie)
>
>     I also tried to config the kernel outside of yocto, downloaded
>     https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.4.tar.xz
>     <https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.4.tar.xz>,
>     extracted and run make menuconfig => works as expected
>
>     Any hints are appreciated.
>
>     Thanks
>     -- 
>     _______________________________________________
>     yocto mailing list
>     yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/yocto
>     <https://lists.yoctoproject.org/listinfo/yocto>
>
>


[-- Attachment #2: Type: text/html, Size: 6653 bytes --]

Re: bitbake menuconfig fails

[Zoran Stojsavljevic]

[-- Attachment #1: Type: text/plain, Size: 5694 bytes --]

Hello Mircea,

I am using just normal YOCTO (rocko), as the test platform to perform
various tests on qemux86-64 and to do some
deeper learning.

My host is Fedora 26 VM (over WIN10 64 PRO, using VMWare Workstation12 as
VMM), and here is CLI transcript
for you:

[user@localhost build]$ uname -r
4.13.16-202.fc26.x86_64
[user@localhost build]$ dnf list installed | grep ncurses
ncurses.x86_64                          6.0-8.20170212.fc26     @anaconda

ncurses-base.noarch                     6.0-8.20170212.fc26     @anaconda

ncurses-c++-libs.x86_64                 6.0-8.20170212.fc26     @fedora

ncurses-compat-libs.x86_64              6.0-8.20170212.fc26     @fedora

ncurses-devel.x86_64                    6.0-8.20170212.fc26     @fedora

ncurses-libs.x86_64                     6.0-8.20170212.fc26     @anaconda

[user@localhost build]$ bitbake -s | grep ncurses
nativesdk-ncurses                            :6.0+20170715-r0

ncurses                                      :6.0+20170715-r0

ncurses-native                               :6.0+20170715-r0

[user@localhost build]$ bitbake script
Loading cache: 100%
|#########################################################################|
Time: 0:00:00
Loaded 1276 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.35.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "qemux86-64"
DISTRO            = "poky"
DISTRO_VERSION    = "2.4"
TUNE_FEATURES     = "m64 core2"
TARGET_FPU        = ""
meta
meta-poky
meta-yocto-bsp
meta-mylayer      = "rocko:65d23bd7986615fdfb0f1717b615534a2a14ab80"

Initialising tasks: 100%
|#########################################################################|
Time: 0:00:01
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 564 tasks of which 564 didn't need to be
rerun and all succeeded.
NOTE: Writing buildhistory
[user@localhost build]$
_______

You can try also these commands by yourself, as basis for further
investigation on your YOCTO distro and host OS you
are using (krogoth, 2.1.2, Debian 8 (jessie).

This also confirms your thoughts, my best guess. :-)

Zoran

On Wed, Dec 6, 2017 at 1:20 PM, Mircea Gliga <mircea.gliga@vitheia.com>
wrote:

> Thanks Zoran
> What you say makes perfect sense.
> I also got the feeling that something doesn't match between the new kernel
> and yocto.
> Maybe I should also upgrade yocto.
>
> Thanks again.
>
>
> On 06/12/17 09:22, Zoran Stojsavljevic wrote:
>
> Hello Mircea,
>
> From my point of view:
>
> *> /usr/bin/ld: cannot find -lncursesw*
> > collect2: error: ld returned 1 exit status
> > scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf'
> failed
>
> The first line explains it all. You could not configure 4.14, since for
> this you should have ncurses package. I would further say, the
> YOCTO ncurses version you have, which is used for 4.8 is outdated, so you
> need newer (matching) YOCTO version for 4.14.
>
> Why you are able to configure 4.14 outside of yocto? Because you use
> another version of ncurses, one which is host native to
> Debian 8. YOCTO probably uses some other host based ncurses inside YOCTO
> (in Open Embedded/meta layer, my best guess).
>
> Zoran
>
> On Wed, Dec 6, 2017 at 7:31 AM, Mircea Gliga <mircea.gliga@vitheia.com>
> wrote:
>
>> Hello
>>
>> We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb)-
>> everything ok.
>> I'm trying to upgrade to 4.14, I created a new recipe
>> linux-stable_4.14.bb. They live side by side, for now.
>> But with the 4.14 kernel when running `bitbake -c menuconfig
>> linux-stable`, the new terminal comes up and I get the following error:
>>
>>   HOSTCC  scripts/basic/fixdep
>>   GEN     ./Makefile
>>   HOSTCC  scripts/kconfig/mconf.o
>>   HOSTCC  scripts/kconfig/zconf.tab.o
>>   HOSTCC  scripts/kconfig/lxdialog/checklist.o
>>   HOSTCC  scripts/kconfig/lxdialog/util.o
>>   HOSTCC  scripts/kconfig/lxdialog/inputbox.o
>>   HOSTCC  scripts/kconfig/lxdialog/textbox.o
>>   HOSTCC  scripts/kconfig/lxdialog/yesno.o
>>   HOSTCC  scripts/kconfig/lxdialog/menubox.o
>>   HOSTLD  scripts/kconfig/mconf
>> /usr/bin/ld: cannot find -lncursesw
>> collect2: error: ld returned 1 exit status
>> scripts/Makefile.host:111: recipe for target 'scripts/kconfig/mconf'
>> failed
>> make[3]: *** [scripts/kconfig/mconf] Error 1
>> /media/mircea/ExtLinux/Adventure/testBuildServer/product-sam
>> a5-kernel/yocto/build/tmp/work-shared/cuxe/kernel-source/Makefile:548:
>> recipe for target 'menuconfig' failed
>> make[2]: *** [menuconfig] Error 2
>> Makefile:146: recipe for target 'sub-make' failed
>> make[1]: *** [sub-make] Error 2
>> Makefile:24: recipe for target '__sub-make' failed
>> make: *** [__sub-make] Error 2
>> Command failed.
>>
>>
>> If I rename linux-stable_4.14.bb to linux-stable_4.14.bb___, then run
>> bitbake again (now the build system is working with the 4.8 kernel again)
>> => menuconfig starts and works as expected.
>>
>> I'm using krogoth, 2.1.2, Debian 8 (jessie)
>>
>> I also tried to config the kernel outside of yocto, downloaded
>> https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.14.4.tar.xz,
>> extracted and run make menuconfig => works as expected
>>
>> Any hints are appreciated.
>>
>> Thanks
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>

[-- Attachment #2: Type: text/html, Size: 10005 bytes --]