[yocto] bitbake -c devshell option

Chris Larson clarson at kergoth.com
Sun Dec 9 12:22:11 PST 2012


On Sun, Dec 9, 2012 at 1:05 PM, Marco <koansoftware at gmail.com> wrote:

> I was used to work with oe-classic.
> When I used oe-classic, often I used the 'devshell' option to try to
> compile (make uImage) the kernel with the entire environment set up
> correctly.
> Now if I do the same procedure with Yocto 8 Danny it does not work.
> For example I'm using a default configuration below:
>
> 1st step
> ---
> MACHINE="beagleboard" bitbake -c devshell virtual/kernel
>
> Build Configuration:
> BB_VERSION        = "1.16.0"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "beagleboard"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.3"
> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp    = "danny:**09031ac2fc0f30ec577ee823fc61ff**0e5d852e21"
>
> NOTE: Resolving any missing task queue dependencies
> NOTE: Preparing runqueue
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> NOTE: Tasks Summary: Attempted 912 tasks of which 912 didn't need to be
> rerun and all succeeded.
>
>
> 2nd step just after 1st
> ------------------------
> MACHINE="beagleboard" bitbake -c devshell virtual/kernel
>
> - Devshell starts in a new screen
> ------------------------
> $ pwd
> ~/yocto-8-danny/poky/build/**tmp/work/beagleboard-poky-**
> linux-gnueabi/linux-yocto-3.4.**11+git1+**a201268353c030d9fafe00f2041976**
> f7437d9386_1+**449f7f520350700858f21a5554b81c**c8ad23267d-r4.3/linux
>
> - lauch a kernel build (as I was used to do)
> ------------------------
> $ make
> scripts/kconfig/conf --silentoldconfig Kconfig
> ***
> *** Configuration file ".config" not found!
> ***
> *** Please run some configurator (e.g. "make oldconfig" or
> *** "make menuconfig" or "make xconfig").
> ***
> make[2]: *** [silentoldconfig] Error 1
> make[1]: *** [silentoldconfig] Error 2
> make: *** No rule to make target `include/config/auto.conf', needed by
> `include/config/kernel.**release'.  Stop.
>
>
> I would like to find out whether you can still do this and what is the new
> way to go
>


devshell runs with the source tree unpacked and patched. It has never
guaranteed that the sources would already be *configured* at that time,
either in oe-classic or current. Run a bitbake -c configure virtual/kernel
first, or just use -c menuconfig.
-- 
Christopher Larson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20121209/cb6d6ee0/attachment.html>


More information about the yocto mailing list