From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: What is expected of a kernel recipe nowadays?
Date: Wed, 7 Jan 2015 11:07:35 +0100 [thread overview]
Message-ID: <20150107100735.GF29986@jama> (raw)
In-Reply-To: <CAJTo0LaW2JLjqHCDEMggAb2QLM+Ns14qQWGq=BG5jLFu4HVRow@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3595 bytes --]
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
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-01-07 10:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 8:03 What is expected of a kernel recipe nowadays? Mike Looijmans
2015-01-05 8:29 ` Mike Looijmans
2015-01-05 20:18 ` Bruce Ashfield
2015-01-06 0:47 ` Otavio Salvador
2015-01-06 7:14 ` Mike Looijmans
2015-01-06 8:57 ` Martin Jansa
2015-01-06 11:04 ` Martin Jansa
2015-01-06 11:33 ` Burton, Ross
2015-01-06 14:08 ` Bruce Ashfield
2015-01-06 11:08 ` Burton, Ross
2015-01-07 10:07 ` Martin Jansa [this message]
2015-01-07 13:08 ` Bruce Ashfield
2015-01-07 15:48 ` Bruce Ashfield
2015-01-07 15:56 ` Martin Jansa
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=20150107100735.GF29986@jama \
--to=martin.jansa@gmail.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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