From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Re: workflow - kernel config
Date: Sat, 05 Nov 2011 08:34:24 +0200 [thread overview]
Message-ID: <j92ldh$6tg$1@dough.gmane.org> (raw)
In-Reply-To: <CADkTA4N=My0k31D2moYzK6gi70r2B9hL_-Bqw5T320pLqGGZ1g@mail.gmail.com>
Hi Bruce,
On 11/04/2011 09:15 PM, Bruce Ashfield wrote:
>
> This is one flow that will work to make changes to the default kernel, and
> test them on a board. I use something like:
>
> bitbake -f -c configure linux-yocto
> bitbake -f -c menuconfig
> bitbake -c linux-yocto
>
> after I've done an initial build/configure phase if I'm updating options.
> But that's likely not the most efficient workflow either (I've got liberal
> use of -f in there, since I'm a bit paranoid).
>
This does not seem to work either - menuconfig is not being invoked:
rber@yocto-1:~/projects/yocto/yocto_for_trainer/sandbox_work$
./03.05-configure-build-poky-kernel.sh
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
----->
make sure INHERIT += "rm_work" is commented out
kernel fiddling will not work with it
press <ENTER> to go on
<-----
Loading cache: 100%
|########################################################################################|
ETA: 00:00:00
Loaded 1036 entries from dependency cache.
OE Build Configuration:
BB_VERSION = "1.13.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "beagleboard"
DISTRO = "poky"
DISTRO_VERSION = "1.1"
TUNE_FEATURES = "armv7a vfp neon cortexa8"
TARGET_FPU = "vfp-neon"
meta
meta-yocto =
"edison-6.0_LOCAL:1924f52cc894d4dd6b9d9c1a2248b32fc0a24c8c"
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 299 of 299 (ID: 6,
/work/rber/poky/meta/recipes-kernel/linux/linux-yocto_2.6.37.bb,
do_configure)
NOTE: package
linux-yocto-2.6.37+git1+aeea99683c7283f1f3320bf2ee7085ee252d4e7e_1+3ddb22772862a8223640fa97580569924f51bddc-r21:
task do_configure: Started
NOTE: package
linux-yocto-2.6.37+git1+aeea99683c7283f1f3320bf2ee7085ee252d4e7e_1+3ddb22772862a8223640fa97580569924f51bddc-r21:
task do_configure: Succeeded
NOTE: Tasks Summary: Attempted 299 tasks of which 298 didn't need to be
rerun and 0 failed.
Nothing to do. Use 'bitbake world' to build everything, or run 'bitbake
--help' for usage information.
Nothing to do. Use 'bitbake world' to build everything, or run 'bitbake
--help' for usage information.
rber@yocto-1:~/projects/yocto/yocto_for_trainer/sandbox_work$
Regards,
Robert..."The wonderful thing about standards is that there are so many
of them to choose from." - (Amazing) Grace Murray Hopper, as quoted in
the Unix Haters Handbook, p.10
My public pgp key is available at:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
next prev parent reply other threads:[~2011-11-05 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 17:23 workflow - kernel config Robert Berger
2011-11-04 18:08 ` Robert Berger
2011-11-04 19:15 ` Bruce Ashfield
2011-11-05 6:34 ` Robert Berger [this message]
2011-11-07 14:39 ` Bruce Ashfield
2011-11-07 16:39 ` Richard Purdie
2011-11-07 17:58 ` Bruce Ashfield
2011-11-08 19:24 ` Darren Hart
2011-11-05 11:27 ` Robert Berger
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='j92ldh$6tg$1@dough.gmane.org' \
--to=gmane@reliableembeddedsystems.com \
--cc=poky@pokylinux.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.