All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: linux: having problems forcing a kernel recompile...
Date: Sat, 10 Jan 2015 17:10:19 -0500	[thread overview]
Message-ID: <54B1A34B.8010109@mindchasers.com> (raw)
In-Reply-To: <CADkTA4NvLdwTnknRvg83B1FNQgOSQg5x66kYo437+mszf=dWrQ@mail.gmail.com>

On 01/10/2015 02:45 PM, Bruce Ashfield wrote:
> On Fri, Jan 9, 2015 at 11:32 AM, Bob Cochran <yocto@mindchasers.com> wrote:
>> Hi,
>>
>> I'm working with the latest poky master branch (as of this morning:
>> 876370419a), and I can't force a recompile of the kernel:
>>
>> $ bitbake virtual/kernel -c compile -f
>>
>> fails with
>>
>> | make[2]: *** [prepare3] Error 1
>>
>> I have seen this with both linux-qoriq and my own derived linux-yocto
>> recipe.
>>
>> I believe it's due to my sysroots kernel source directory not being clean.
>>
>> When I initially bake my kernel, I can see that the do_populate_sysroot task
>> is run and it copies a .config into sysroots/<machine>/usr/src/kernel.
>>
>> When I try to force the recompile, MAKE sees that my source directory isn't
>> clean and quits ( throws the prepare3 error ).
>>
>> Somewhat related, I also notice that neither a
>>
>> $ bitbake virtual/kernel -c cleansstate
>>
>> nor a
>>
>> $ bitbake virtual/kernel -c cleanall
>>
>> actually cleans my kernel source directory.  Should it?
>>
>>
>> If these are legitimate bugs, I'll be happy to file a bugzilla report.
>
>
> These are due to some changes that we merged at the end of December to
> improve kernel build times. We have bugs open for this issue, and set of
> changes nearly ready that addresses this, and a few other pending issues.


Thanks Bruce for letting me know.  It's easy to work around - just 
delete .config & include/config from sysroot.




>
> Bruce
>
>>
>>
>> Thanks
>>
>> Bob
>>
>>
>>
>>
>>
>> Error Log from running "bitbake virtual/kernel -c compile -f":
>>
>>
>> | DEBUG: Executing shell function do_compile
>> | NOTE: make -j 4 uImage CC=powerpc64-poky-linux-gcc
>> --sysroot=/build/yocto/t1040_1/tmp/sysroots/t1040rdb-64b
>> LD=powerpc64-poky-linux-ld.bfd
>> --sysroot=/build/yocto/t1040_1/tmp/sysroots/t1040rdb-64b
>> |   CHK     include/config/kernel.release
>> |   GEN
>> /build/yocto/t1040_1/tmp/work/t1040rdb_64b-poky-linux/linux-qoriq/3.12-r0/build/Makefile
>> |   CHK     include/generated/uapi/linux/version.h
>> |   Using /build/yocto/t1040_1/tmp/sysroots/t1040rdb-64b/usr/src/kernel as
>> source for kernel
>> |   /build/yocto/t1040_1/tmp/sysroots/t1040rdb-64b/usr/src/kernel is not
>> clean, please run 'make mrproper'
>> |   in the '/build/yocto/t1040_1/tmp/sysroots/t1040rdb-64b/usr/src/kernel'
>> directory.
>> |   CHK     include/generated/utsrelease.h
>> | make[2]: *** [prepare3] Error 1
>> | make[2]: *** Waiting for unfinished jobs....
>> |   CC      scripts/mod/empty.o
>> |   CC      scripts/mod/devicetable-offsets.s
>> |   MKELF   scripts/mod/elfconfig.h
>> |   HOSTCC  scripts/mod/modpost.o
>> |   HOSTCC  scripts/mod/sumversion.o
>> |   GEN     scripts/mod/devicetable-offsets.h
>> |   HOSTCC  scripts/mod/file2alias.o
>> |   HOSTLD  scripts/mod/modpost
>> | make[1]: *** [sub-make] Error 2
>> | make: *** [all] Error 2
>> | ERROR: oe_runmake failed
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>



  reply	other threads:[~2015-01-10 22:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 16:32 linux: having problems forcing a kernel recompile Bob Cochran
2015-01-10 19:45 ` Bruce Ashfield
2015-01-10 22:10   ` Bob Cochran [this message]
2015-01-10 22:37   ` Bob Cochran
2015-01-11 19:55     ` Bruce Ashfield

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=54B1A34B.8010109@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=bruce.ashfield@gmail.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.