Re: What is expected of a kernel recipe nowadays?

[Martin Jansa <martin.jansa@gmail.com>]

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

On Wed, Jan 07, 2015 at 10:48:50AM -0500, Bruce Ashfield wrote:
> On Wed, Jan 7, 2015 at 5:07 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Tue, Jan 06, 2015 at 11:08:53AM +0000, Burton, Ross wrote:
> >> On 6 January 2015 at 08:57, Martin Jansa <martin.jansa@gmail.com> wrote:
> >>
> >> > 2) do_configure failing:
> >> >
> >> > ERROR: Function failed: do_configure (log file is located at
> >> > /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
> >> > ERROR: Logfile of failure stored in:
> >> > /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498
> >> > Log data follows:
> >> > | DEBUG: Executing python function sysroot_cleansstate
> >> > | DEBUG: Python function sysroot_cleansstate finished
> >> > | DEBUG: Executing shell function do_configure
> >> > | NOTE: make oldconfig
> >> > | make: *** No rule to make target `oldconfig'.  Stop.
> >> > | ERROR: oe_runmake failed
> >> > | WARNING: exit code 1 from a shell command.
> >> > | ERROR: Function failed: do_configure (log file is located at
> >> > /home/jenkins/workspace/luneos-unstable/webos-ports/tmp-glibc/work/mako-webos-linux-gnueabi/linux-lg-mako/3.4.0+gitrAUTOINC+38bdbfe224-r0/temp/log.do_configure.17498)
> >> > NOTE: recipe linux-lg-mako-3.4.0+gitrAUTOINC+38bdbfe224-r0: task
> >> > do_configure: Failed
> >> > ERROR: Task 491
> >> > (/home/jenkins/workspace/luneos-unstable/webos-ports/meta-smartphone/meta-lg/recipes-kernel/linux/
> >> > linux-lg-mako_git.bb, do_configure) failed with exit code '1'
> >> >
> >>
> >> I'll Me Too here, often hitting this on rebuilds:
> >>
> >> DEBUG: Executing shell function do_configure
> >> NOTE: make -C /data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel
> >> O=/data/poky-master/tmp/work/qemuarm64-poky-linux/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_902f34d361-r0/linux-qemuarm64-standard-build
> >> oldnoconfig
> >> make: Entering directory
> >> `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel'
> >> make: *** No rule to make target `oldnoconfig'.  Stop.
> >> make: Leaving directory
> >> `/data/poky-master/tmp/sysroots/qemuarm64/usr/src/kernel' ERROR: Task 77
> >> (/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
> >> do_configure) failed with exit code '1'
> >
> > last world build revealed new kind of error:
> >
> > both qemux86 and qemux86-64 failed like this
> >
> > ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
> > ERROR: Logfile of failure stored in: /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974
> > Log data follows:
> > | DEBUG: Executing shell function do_kernel_configme
> > | NOTE: kernel configme
> > | [INFO] Configuring target/machine combo: "standard/qemux86-64"
> > | [INFO] collecting configs in .meta/meta-series
> > | ERROR: could not sanitize configuration fragments
> > |    errors are logged in /home/jenkins/oe/world/shr-core/tmp-glibc/sysroots/qemux86-64/usr/src/kernel/.meta/cfg/standard/common-pc-64/config.log
> > | WARNING: exit code 1 from a shell command.
> > | ERROR: Function failed: do_kernel_configme (log file is located at /home/jenkins/oe/world/shr-core/tmp-glibc/work/qemux86_64-oe-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/temp/log.do_kernel_configme.6974)
> > NOTE: recipe linux-yocto-3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0: task do_kernel_configme: Failed
> 
> I spoke to soon before. Where can I find the config that triggered this ? I just
> built the latest master and my fragments/patches were all properly applied in
> the default build:

It's random, the same oe-core revision first built it fine, then it
failed, then it again built fine, see:
http://www.openembedded.org/wiki/Bitbake_World_Status
the successful build isn't there yet, but rebuilding from the same
sstate finished kernel fine

> -------------------------
> 
> DEBUG: Executing shell function do_kernel_configme
> NOTE: kernel configme
> [INFO] Configuring target/machine combo: "standard/qemux86-64"
> [INFO] collecting configs in .meta/meta-series
> [INFO] Pre-processed cfg file qemux86-64-standard-config-3.17.6 created.
> [INFO] processing of raw cfg data completed.
> 
> ********************************************************************************
>   Configuration stored in
> /home/bruce/oe/build/tmp/work/qemux86_64-poky-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/linux-qemux86_64-standard-build/.config
> ********************************************************************************
> 
>   To build with this kernel configuration, ensure a suitable toolchain
>   is in your path for x86_64, note its common command prefix, and do:
> 
>    make O=/home/bruce/oe/build/tmp/work/qemux86_64-poky-linux/linux-yocto/3.17.6+gitAUTOINC+b81030f9ec_5ff54d8fbf-r0/linux-qemux86_64-standard-build
> ARCH=x86_64 \
>         CROSS_COMPILE=<cross-compile-prefix>
> 
> DEBUG: Shell function do_kernel_configme finished
> 
> -------------------------
> 
> Bruce
> 
> >
> > --
> > Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
> >
> > --
> > _______________________________________________
> > 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"

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]