From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: linux-yocto: bitbake restarts with do_fetch after a -c configure
Date: Wed, 17 Aug 2011 09:15:33 -0700 [thread overview]
Message-ID: <4E4BE925.1070605@linux.intel.com> (raw)
I was having some trouble doing some iterative kernel development and
noticed that bitbake was restarting with do_fetch no matter what stage I
had completed with the previous command. I thought it might be
triggering on a source change, but just running the following without
any other changes had the same result:
$ bitbake linux-yocto -c configure
...
$ bitbake linux-yocto
$ bitbake linux-yocto
Loading cache: 100%
|######################################################################################################|
ETA: 00:00:00
Loaded 1019 entries from dependency cache.
Parsing recipes: 100%
|####################################################################################################|
Time: 00:00:01
Parsing of 790 .bb files complete (788 cached, 2 parsed). 1020 targets,
37 skipped, 0 masked, 0 errors.
OE Build Configuration:
BB_VERSION = "1.13.3"
TARGET_ARCH = "powerpc"
TARGET_OS = "linux"
MACHINE = "qemuppc"
DISTRO = "poky"
DISTRO_VERSION = "1.0+snapshot-20110817"
TUNE_FEATURES = "m32 fpu-hard ppc603e"
TARGET_FPU = ""
meta
meta-yocto = "master:288c947ee69131cc29e9c367523cc71e4df56a76"
meta-kernel-dev = "master:5193f2986c82d4c9a3b5e3cffb96877406664151"
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 484 of 860 (ID: 6,
/home/dvhart/source/poky.git/meta/recipes-kernel/linux/linux-yocto_2.6.37.bb,
do_fetch)
This prevents any sort of iterative development as the unpack and
subsequent steps undue any local changes to the source tree. This
appears to be a regression.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
reply other threads:[~2011-08-17 16:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E4BE925.1070605@linux.intel.com \
--to=dvhart@linux.intel.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.