linux recipe selected despite ASSUME_PROVIDED += "virtual/kernel"

linux recipe selected despite ASSUME_PROVIDED += "virtual/kernel"

[Graham Gower]

Hi,
I wish to build an Angstrom based console-image for mipsel from the
org.openembedded.dev branch. I maintain a kernel for the device but am
not yet ready to integrate this into an OE recipe. The default linux_2.6.30.bb
fails to build for me, thus I wish to not build the kernel at this point
in time.

My local.conf contains the following lines,
STAGING_KERNEL_DIR = "/home/grg/jz/linux"
ASSUME_PROVIDED += "virtual/kernel"

However, when i run 'bitbake console-image the default linux_2.6.30.bb recipe
is still selected and the build procedes to fail.

Is this the correct procedure to avoid building a kernel? If so, what else
could I be doing wrongly?

-Graham

Re: linux recipe selected despite ASSUME_PROVIDED += "virtual/kernel"

[Patrick Bellasi]

On Mon, Jul 27, 2009 at 09:50, Graham Gower<graham.gower@gmail.com> wrote:
> Hi,
> I wish to build an Angstrom based console-image for mipsel from the
> org.openembedded.dev branch. I maintain a kernel for the device but am
> not yet ready to integrate this into an OE recipe. The default
> linux_2.6.30.bb
> fails to build for me, thus I wish to not build the kernel at this point
> in time.
>
> My local.conf contains the following lines,
> STAGING_KERNEL_DIR = "/home/grg/jz/linux"
> ASSUME_PROVIDED += "virtual/kernel"

I guess that a kernel is required to build an image: in instance to
compile libc which relay on some kernel headers.

> However, when i run 'bitbake console-image the default linux_2.6.30.bb
> recipe
> is still selected and the build procedes to fail.
>
> Is this the correct procedure to avoid building a kernel? If so, what else
> could I be doing wrongly?
So: if you ASSUME_PROVIDED a kernel, at least you should provide a
reference to you kernel tree... but the main poin is: is it possible
to reference a kernel outside OE?

>
> -Graham

Patrick

-- 
#include <best/regards.h>

DERKLING
LRU 338214 (http://counter.li.org)

<---------------------------------------------------------------------------------------------------------->
   Patrick Bellasi <bellasi at elet dot polimi dot it>
   PhD student at Politecnico di Milano

   Contacts:
    - ICQ         344672588
    - MSN       derkling at yahoo dot it
    - Skype     derkling

   Personal Sites:
    - Bookmarks
           http://del.icio.us/derkling
    - Bibliography
           http://www.bibsonomy.org/user/derkling

   Privacy:
    - GnuPG     0x72ABC1EE (keyserver.linux.it)
       pub      1024D/72ABC1EE 2003-12-04
       Key fingerprint = 3958 7B5F 36EC D1F8 C752
                                9589 C3B7 FD49 72AB C1EE
<---------------------------------------------------------------------------------------------------------->

Re: linux recipe selected despite ASSUME_PROVIDED += "virtual/kernel"

[Graham Gower]

2009/7/27 Patrick Bellasi <derkling@gmail.com>:
> On Mon, Jul 27, 2009 at 09:50, Graham Gower<graham.gower@gmail.com> wrote:
>> Hi,
>> I wish to build an Angstrom based console-image for mipsel from the
>> org.openembedded.dev branch. I maintain a kernel for the device but am
>> not yet ready to integrate this into an OE recipe. The default
>> linux_2.6.30.bb
>> fails to build for me, thus I wish to not build the kernel at this point
>> in time.
>>
>> My local.conf contains the following lines,
>> STAGING_KERNEL_DIR = "/home/grg/jz/linux"
>> ASSUME_PROVIDED += "virtual/kernel"
>
> I guess that a kernel is required to build an image: in instance to
> compile libc which relay on some kernel headers.
>
>> However, when i run 'bitbake console-image the default linux_2.6.30.bb
>> recipe
>> is still selected and the build procedes to fail.
>>
>> Is this the correct procedure to avoid building a kernel? If so, what else
>> could I be doing wrongly?
> So: if you ASSUME_PROVIDED a kernel, at least you should provide a
> reference to you kernel tree... but the main poin is: is it possible
> to reference a kernel outside OE?

Yes, I had hoped setting the STAGING_KERNEL_DIR would do what you say.

Re: linux recipe selected despite ASSUME_PROVIDED += "virtual/kernel"

[Martyn Welch]

Graham Gower wrote:
> Hi,
> I wish to build an Angstrom based console-image for mipsel from the
> org.openembedded.dev branch. I maintain a kernel for the device but am
> not yet ready to integrate this into an OE recipe. The default 
> linux_2.6.30.bb
> fails to build for me, thus I wish to not build the kernel at this point
> in time.
>
> My local.conf contains the following lines,
> STAGING_KERNEL_DIR = "/home/grg/jz/linux"
> ASSUME_PROVIDED += "virtual/kernel"
>
> However, when i run 'bitbake console-image the default linux_2.6.30.bb 
> recipe
> is still selected and the build procedes to fail.
>
> Is this the correct procedure to avoid building a kernel? If so, what 
> else
> could I be doing wrongly?

I tend to create a bitbake recipe to build my kernel and put it in an 
overlay, otherwise known as a collection[1] and setting the 
"DEFAULT_PREFERENCE"[2] to a large positive number to cause the build to 
prefer that kernel. That way it's building your kernel, but it's not yet 
in the org.openembedded.dev branch.

Martyn

[1] 
http://docs.openembedded.org/usermanual/usermanual.html#special_bitbake_collections
[2] 
http://docs.openembedded.org/usermanual/usermanual.html#recipes_defaultpreference

-- 
Martyn Welch MEng MPhil MIET (Principal Software Engineer)   T:+44(0)1327322748
GE Fanuc Intelligent Platforms Ltd,        |Registered in England and Wales
Tove Valley Business Park, Towcester,      |(3828642) at 100 Barbirolli Square,
Northants, NN12 6PF, UK T:+44(0)1327359444 |Manchester,M2 3AB  VAT:GB 927559189

Re: linux recipe selected despite ASSUME_PROVIDED += "virtual/kernel"

[Koen Kooi]

On 27-07-09 10:46, Patrick Bellasi wrote:
> On Mon, Jul 27, 2009 at 09:50, Graham Gower<graham.gower@gmail.com>  wrote:
>> Hi,
>> I wish to build an Angstrom based console-image for mipsel from the
>> org.openembedded.dev branch. I maintain a kernel for the device but am
>> not yet ready to integrate this into an OE recipe. The default
>> linux_2.6.30.bb
>> fails to build for me, thus I wish to not build the kernel at this point
>> in time.
>>
>> My local.conf contains the following lines,
>> STAGING_KERNEL_DIR = "/home/grg/jz/linux"
>> ASSUME_PROVIDED += "virtual/kernel"
>
> I guess that a kernel is required to build an image: in instance to
> compile libc which relay on some kernel headers.

Bzzzt! Wrong! OE builds the libc headers from a different recipe called 
linux-libc-headers.

regards,

Koen