From: Gary Thomas <gary@mlbassoc.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Yocto Project <yocto@yoctoproject.org>
Subject: Re: Kernel build woes
Date: Wed, 21 Jan 2015 10:02:34 -0700 [thread overview]
Message-ID: <54BFDBAA.30104@mlbassoc.com> (raw)
In-Reply-To: <54BFCF0D.1060108@windriver.com>
On 2015-01-21 09:08, Bruce Ashfield wrote:
> On 15-01-21 11:02 AM, Gary Thomas wrote:
>> Since the recent changes in how the kernel is built, some useful
>> workflows have been broken. In particular when working on a
>> kernel, I use this sequence quite a lot:
>> $ bitbake virtual/kernel
>> $ bitbake virtual/kernel -c devshell
>> ... make some tweaks, add a test patch, etc
>> $ bitbake virtual/kernel -C compile
>>
>> Trying this with a quite recent master
>> (4e20211090d2b193250edaa64f84e355a1c31fe5)
>> I get this error on the compile step:
>>
>> ERROR: Function failed: do_compile (log file is located at
>> /home/local/qemuarm_2015-01-09/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0/temp/log.do_compile.29205)
>>
>> ERROR: Logfile of failure stored in:
>> /home/local/qemuarm_2015-01-09/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0/temp/log.do_compile.29205
>>
>> Log data follows:
>> | DEBUG: Executing shell function do_compile
>> | NOTE: make -j 4 zImage CC=arm-poky-linux-gnueabi-gcc
>> -mno-thumb-interwork -marm LD=arm-poky-linux-gnueabi-ld.bfd
>> | CHK include/config/kernel.release
>> | Using
>> /home/local/qemuarm_2015-01-09/tmp/sysroots/qemuarm/usr/src/kernel as
>> source for kernel
>> | /home/local/qemuarm_2015-01-09/tmp/sysroots/qemuarm/usr/src/kernel
>> is not clean, please run 'make mrproper'
>> | in the
>> '/home/local/qemuarm_2015-01-09/tmp/sysroots/qemuarm/usr/src/kernel'
>> directory.
>> | make[2]: *** [prepare3] Error 1
>> | make[1]: *** [sub-make] Error 2
>> | make: *** [all] Error 2
>> | ERROR: oe_runmake failed
>> | WARNING:
>> /home/local/qemuarm_2015-01-09/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0/temp/run.do_compile.29205:1
>> exit 1 from
>> | exit 1
>> | ERROR: Function failed: do_compile (log file is located at
>> /home/local/qemuarm_2015-01-09/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto/3.14.24+gitAUTOINC+a227f20eff_6166316d47-r0/temp/log.do_compile.29205)
>>
>> ERROR: Task 10
>> (/home/local/poky-cutting-edge/meta/recipes-kernel/linux/linux-yocto_3.14.bb,
>> do_compile) failed with exit code '1'
>>
>> Note: this is not unique to the linux-yocto recipe, I've seen
>> the same error when using some kernel recipes from meta-fsl-arm*,
>> e.g. linux-boundary, as well as some local recipes which inherit
>> kernel.bbclass
>>
>> Should I file this as a bug?
>
> This has already been addressed in master as of Monday. The kernel is
> in tmp/build/work-shared/, and can handle this sort of workflow.
>
> Bruce
>
Indeed, it works again after updating to the latest master.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2015-01-21 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 16:02 Kernel build woes Gary Thomas
2015-01-21 16:08 ` Bruce Ashfield
2015-01-21 17:02 ` Gary Thomas [this message]
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=54BFDBAA.30104@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=bruce.ashfield@windriver.com \
--cc=yocto@yoctoproject.org \
/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 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.