* Build error in kernel-module-imx-gpu-viv when building linux-boundary kernel explicitely first
@ 2016-03-18 10:39 Carlos Rafael Giani
2016-03-21 13:17 ` Otavio Salvador
0 siblings, 1 reply; 2+ messages in thread
From: Carlos Rafael Giani @ 2016-03-18 10:39 UTC (permalink / raw)
To: meta-freescale@yoctoproject.org
I noticed a build error when building a rootfs for nitrogen6x.
I first ran: MACHINE=nitrogen6x nice bitbake virtual/kernel
Then, MACHINE=nitrogen6x nice bitbake kernel-module-imx-gpu-viv
and I got the compile error attached below.
Then I ran: MACHINE=nitrogen6x nice bitbake -c cleansstate
kernel-module-imx-gpu-viv virtual/kernel
and: MACHINE=nitrogen6x nice bitbake kernel-module-imx-gpu-viv (letting
bitbake build the kernel automatically as a dependency)
and the error did not appear. Neither does it happen if I just build an
image directly. Only if I explicitley build the kernel first it breaks.
This is using latest master in poky, meta-openembedded, meta-fsl-arm,
meta-fsl-arm-extra.
Any ideas why this happens?
===== compile error =====:
ERROR:
kernel-module-imx-gpu-viv-5.0.11.p7.4+fslc+gitAUTOINC+2b3290d1c1-r0
do_make_scripts: Function failed: do_make_scripts (log file is located
at
/home/build/BuildSetups/yocto-master/poky/build/tmp/work/nitrogen6x-poky-linux-gnueabi/kernel-module-imx-gpu-viv/5.0.11.p7.4+fslc+gitAUTOINC+2b3290d1c1-r0/temp/log.do_make_scripts.17831)
ERROR: Logfile of failure stored in:
/home/build/BuildSetups/yocto-master/poky/build/tmp/work/nitrogen6x-poky-linux-gnueabi/kernel-module-imx-gpu-viv/5.0.11.p7.4+fslc+gitAUTOINC+2b3290d1c1-r0/temp/log.do_make_scripts.17831
Log data follows:
| DEBUG: Executing shell function do_make_scripts
| make: Entering directory
'/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source'
| HOSTCC scripts/basic/fixdep
| GEN
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-build-artifacts/Makefile
| HOSTCC scripts/kconfig/conf.o
| SHIPPED scripts/kconfig/zconf.tab.c
| SHIPPED scripts/kconfig/zconf.lex.c
| SHIPPED scripts/kconfig/zconf.hash.c
| HOSTCC scripts/kconfig/zconf.tab.o
| In file included from scripts/kconfig/zconf.tab.c:2537:0:
|
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/scripts/kconfig/menu.c:
In function 'get_symbol_str':
|
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/scripts/kconfig/menu.c:587:18:
warning: 'jump' may be used uninitialized in this function
[-Wmaybe-uninitialized]
| jump->offset = strlen(r->s);
| ^
|
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/scripts/kconfig/menu.c:548:19:
note: 'jump' was declared here
| struct jump_key *jump;
| ^
| HOSTLD scripts/kconfig/conf
| scripts/kconfig/conf --silentoldconfig Kconfig
| ***
| *** Configuration file ".config" not found!
| ***
| *** Please run some configurator (e.g. "make oldconfig" or
| *** "make menuconfig" or "make xconfig").
| ***
|
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/scripts/kconfig/Makefile:36:
recipe for target 'silentoldconfig' failed
| make[3]: *** [silentoldconfig] Error 1
|
/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source/Makefile:512:
recipe for target 'silentoldconfig' failed
| make[2]: *** [silentoldconfig] Error 2
| make[1]: *** No rule to make target 'include/config/auto.conf', needed
by 'scripts'. Stop.
| Makefile:133: recipe for target 'sub-make' failed
| make: *** [sub-make] Error 2
| make: Leaving directory
'/home/build/BuildSetups/yocto-master/poky/build/tmp/work-shared/nitrogen6x/kernel-source'
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_make_scripts (log file is located at
/home/build/BuildSetups/yocto-master/poky/build/tmp/work/nitrogen6x-poky-linux-gnueabi/kernel-module-imx-gpu-viv/5.0.11.p7.4+fslc+gitAUTOINC+2b3290d1c1-r0/temp/log.do_make_scripts.17831)
ERROR: Task 6
(/home/build/BuildSetups/yocto-master/meta-fsl-arm/recipes-kernel/kernel-modules/kernel-module-imx-gpu-viv_5.0.11.p7.4+fslc.bb,
do_make_scripts) failed with exit code '1'
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Build error in kernel-module-imx-gpu-viv when building linux-boundary kernel explicitely first
2016-03-18 10:39 Build error in kernel-module-imx-gpu-viv when building linux-boundary kernel explicitely first Carlos Rafael Giani
@ 2016-03-21 13:17 ` Otavio Salvador
0 siblings, 0 replies; 2+ messages in thread
From: Otavio Salvador @ 2016-03-21 13:17 UTC (permalink / raw)
To: Carlos Rafael Giani; +Cc: meta-freescale@yoctoproject.org
Hello Carlos,
On Fri, Mar 18, 2016 at 7:39 AM, Carlos Rafael Giani
<dv@pseudoterminal.org> wrote:
> I noticed a build error when building a rootfs for nitrogen6x.
>
> I first ran: MACHINE=nitrogen6x nice bitbake virtual/kernel
> Then, MACHINE=nitrogen6x nice bitbake kernel-module-imx-gpu-viv
>
> and I got the compile error attached below.
>
> Then I ran: MACHINE=nitrogen6x nice bitbake -c cleansstate
> kernel-module-imx-gpu-viv virtual/kernel
> and: MACHINE=nitrogen6x nice bitbake kernel-module-imx-gpu-viv (letting
> bitbake build the kernel automatically as a dependency)
>
> and the error did not appear. Neither does it happen if I just build an
> image directly. Only if I explicitley build the kernel first it breaks.
>
> This is using latest master in poky, meta-openembedded, meta-fsl-arm,
> meta-fsl-arm-extra.
>
> Any ideas why this happens?
I tried to reproduce the error but it always worked for me. Could you
try to reproduce it one time more?
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-03-21 13:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-03-18 10:39 Build error in kernel-module-imx-gpu-viv when building linux-boundary kernel explicitely first Carlos Rafael Giani
2016-03-21 13:17 ` Otavio Salvador
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.