bitbake -c devshell option

bitbake -c devshell option

[Marco]

Hello,
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:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"

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+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-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

TIA
-- 
Marco Cavallini

Re: bitbake -c devshell option

[Chris Larson]

[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]

On Sun, Dec 9, 2012 at 1:05 PM, Marco <koansoftware@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

[-- Attachment #2: Type: text/html, Size: 3132 bytes --]

Re: bitbake -c devshell option

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 3340 bytes --]

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

> Hello,
> 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
>

As Chris said, this way should still work, and it does work here for me.
There's
one thing that you may notice with kernel's that have split source/build
dirs
(like linux-yocto), is that once you have gone through the configure phase
and drop into the devshell you may not have KBUILT_OUTPUT set to the
build directory, and end up dropping files in the source dir .. which
causes you
mrproper and build issue.

I have a local append to devshell that sets:

      d.setVar("KBUILD_OUTPUT", "${B}")

To make sure things work.  If you need something like this as well, or have
problems with linux-yocot, I can arrange to have something like this added
by default. But since no one else has asked about it, I assumed no one else
is either using devshell, or they haven't run into it.

Cheers,

Bruce




>
> TIA
> --
> Marco Cavallini
> ______________________________**_________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto>
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 4669 bytes --]

Re: bitbake -c devshell option

[Marco C.]

2012/12/9 Bruce Ashfield <bruce.ashfield@gmail.com>:

> As Chris said, this way should still work, and it does work here for me.
> There's
> one thing that you may notice with kernel's that have split source/build
> dirs
> (like linux-yocto), is that once you have gone through the configure phase
> and drop into the devshell you may not have KBUILT_OUTPUT set to the
> build directory, and end up dropping files in the source dir .. which causes
> you
> mrproper and build issue.
>
> I have a local append to devshell that sets:
>
>       d.setVar("KBUILD_OUTPUT", "${B}")
>
> To make sure things work.  If you need something like this as well, or have
> problems with linux-yocot, I can arrange to have something like this added
> by default. But since no one else has asked about it, I assumed no one else
> is either using devshell, or they haven't run into it.
>
> Cheers,
>
> Bruce


Dear Bruce,
I'd like to have the same behaviour as before, so what you suggested
would suit me.
Could you please tell me where to add that line?
Fileneme and function.

Thank you
 --
Marco Cavallini

2012/12/9 Bruce Ashfield <bruce.ashfield@gmail.com>:
>
>
>
> On Sun, Dec 9, 2012 at 3:05 PM, Marco <koansoftware@gmail.com> wrote:
>>
>> Hello,
>> 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:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"
>>
>> 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+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-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
>
>
> As Chris said, this way should still work, and it does work here for me.
> There's
> one thing that you may notice with kernel's that have split source/build
> dirs
> (like linux-yocto), is that once you have gone through the configure phase
> and drop into the devshell you may not have KBUILT_OUTPUT set to the
> build directory, and end up dropping files in the source dir .. which causes
> you
> mrproper and build issue.
>
> I have a local append to devshell that sets:
>
>       d.setVar("KBUILD_OUTPUT", "${B}")
>
> To make sure things work.  If you need something like this as well, or have
> problems with linux-yocot, I can arrange to have something like this added
> by default. But since no one else has asked about it, I assumed no one else
> is either using devshell, or they haven't run into it.
>
> Cheers,
>
> Bruce
>
>
>
>>
>>
>> TIA
>> --
>> Marco Cavallini
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee at
> its end"

Re: bitbake -c devshell option

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 5184 bytes --]

On 12-12-18 10:45 AM, Marco C. wrote:
> 2012/12/9 Bruce Ashfield <bruce.ashfield@gmail.com>:
>
>> As Chris said, this way should still work, and it does work here for me.
>> There's
>> one thing that you may notice with kernel's that have split source/build
>> dirs
>> (like linux-yocto), is that once you have gone through the configure phase
>> and drop into the devshell you may not have KBUILT_OUTPUT set to the
>> build directory, and end up dropping files in the source dir .. which causes
>> you
>> mrproper and build issue.
>>
>> I have a local append to devshell that sets:
>>
>>        d.setVar("KBUILD_OUTPUT", "${B}")
>>
>> To make sure things work.  If you need something like this as well, or have
>> problems with linux-yocot, I can arrange to have something like this added
>> by default. But since no one else has asked about it, I assumed no one else
>> is either using devshell, or they haven't run into it.
>>
>> Cheers,
>>
>> Bruce
>
>
> Dear Bruce,
> I'd like to have the same behaviour as before, so what you suggested
> would suit me.
> Could you please tell me where to add that line?
> Fileneme and function.

Apply the patch to your yocto/oe-core repository (master branch, but
it should apply to danny as well). This will be part of my next
consolidated kernel pull request, so you'll only need to carry
it locally for a short time.

Cheers,

Bruce

>
> Thank you
>   --
> Marco Cavallini
>
> 2012/12/9 Bruce Ashfield <bruce.ashfield@gmail.com>:
>>
>>
>>
>> On Sun, Dec 9, 2012 at 3:05 PM, Marco <koansoftware@gmail.com> wrote:
>>>
>>> Hello,
>>> 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:09031ac2fc0f30ec577ee823fc61ff0e5d852e21"
>>>
>>> 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+a201268353c030d9fafe00f2041976f7437d9386_1+449f7f520350700858f21a5554b81cc8ad23267d-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
>>
>>
>> As Chris said, this way should still work, and it does work here for me.
>> There's
>> one thing that you may notice with kernel's that have split source/build
>> dirs
>> (like linux-yocto), is that once you have gone through the configure phase
>> and drop into the devshell you may not have KBUILT_OUTPUT set to the
>> build directory, and end up dropping files in the source dir .. which causes
>> you
>> mrproper and build issue.
>>
>> I have a local append to devshell that sets:
>>
>>        d.setVar("KBUILD_OUTPUT", "${B}")
>>
>> To make sure things work.  If you need something like this as well, or have
>> problems with linux-yocot, I can arrange to have something like this added
>> by default. But since no one else has asked about it, I assumed no one else
>> is either using devshell, or they haven't run into it.
>>
>> Cheers,
>>
>> Bruce
>>
>>
>>
>>>
>>>
>>> TIA
>>> --
>>> Marco Cavallini
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>>
>> --
>> "Thou shalt not follow the NULL pointer, for chaos and madness await thee at
>> its end"
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


[-- Attachment #2: 0001-kernel-yocto-add-KBUILD_OUTPUT-to-OE_TERMINAL_EXPORT.patch --]
[-- Type: text/x-patch, Size: 1102 bytes --]

From 0f0092ea9091765ab30d83d6574831083e3870c1 Mon Sep 17 00:00:00 2001
From: Bruce Ashfield <bruce.ashfield@windriver.com>
Date: Tue, 18 Dec 2012 12:54:20 -0500
Subject: [PATCH] kernel-yocto: add KBUILD_OUTPUT to OE_TERMINAL_EXPORTS

Since linux-yocto based recipes have a split build and source directory,
we should export KBUILD=${B} to the devshell. This allows the kernel to
be incrementally build within the shell and not dirty the source
directory (which breaks subsequent full builds).

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/classes/kernel-yocto.bbclass |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 793921f..b336e43 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -344,5 +344,6 @@ do_kernel_link_vmlinux() {
 	ln -sf ../../../vmlinux
 }
 
-OE_TERMINAL_EXPORTS += "GUILT_BASE"
+OE_TERMINAL_EXPORTS += "GUILT_BASE KBUILD_OUTPUT"
 GUILT_BASE = "meta"
+KBUILD_OUTPUT = "${B}"
-- 
1.7.10.4