Broken kernel recipes

Broken kernel recipes

[Tom Rini]

Hello,

As part of testing meta-toolchain-sbox builds on different arches, I
found that sbrsh, on ARM, brings in both the 2.6 kernel for the MACHINE
in question, as well as a 2.4 kernel.  In the case of the 2.4 kernel, it
first picks up poodle-kernel-2.4-embedix.bb on nokia800, which doesn't
work as it wants gcc-2.95, which doesn't exist.  Can I move the
following support to packages/obsolete/linux/ ?
corgi-kernel-2.4-embedix.bb
husky-kernel-2.4-embedix.bb
openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.bb
poodle255-kernel-2.4-embedix.bb
poodle-kernel-2.4-embedix.bb
shepherd-kernel-2.4-embedix.bb
openzaurus-pxa27x_2.4.20-rmk2-embedix20050602.bb
openzaurus-sa_2.4.18-rmk7-pxa3-embedix20030509.bb

-- 
Tom Rini

Re: Broken kernel recipes

[Andrea Adami]

For fixes pls. see bug 4784

Andrea

Re: Broken kernel recipes

[Richard Purdie]

On Sat, 2008-12-06 at 19:11 -0700, Tom Rini wrote:
> As part of testing meta-toolchain-sbox builds on different arches, I
> found that sbrsh, on ARM, brings in both the 2.6 kernel for the MACHINE
> in question, as well as a 2.4 kernel.  In the case of the 2.4 kernel, it
> first picks up poodle-kernel-2.4-embedix.bb on nokia800, which doesn't
> work as it wants gcc-2.95, which doesn't exist.  Can I move the
> following support to packages/obsolete/linux/ ?
> corgi-kernel-2.4-embedix.bb
> husky-kernel-2.4-embedix.bb
> openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.bb
> poodle255-kernel-2.4-embedix.bb
> poodle-kernel-2.4-embedix.bb
> shepherd-kernel-2.4-embedix.bb
> openzaurus-pxa27x_2.4.20-rmk2-embedix20050602.bb
> openzaurus-sa_2.4.18-rmk7-pxa3-embedix20030509.bb

These are needed for sharprom-compat. The more interesting question is
why they were being brought in - the 2.6 version should provide
everything they do and have preference?

Cheers,

Richard

Re: Broken kernel recipes

[Koen Kooi]

On 07-12-08 03:11, Tom Rini wrote:
> Hello,
>
> As part of testing meta-toolchain-sbox builds on different arches, I
> found that sbrsh, on ARM, brings in both the 2.6 kernel for the MACHINE
> in question, as well as a 2.4 kernel.  In the case of the 2.4 kernel, it
> first picks up poodle-kernel-2.4-embedix.bb on nokia800, which doesn't
> work as it wants gcc-2.95, which doesn't exist.  Can I move the
> following support to packages/obsolete/linux/ ?
> corgi-kernel-2.4-embedix.bb
> husky-kernel-2.4-embedix.bb
> openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.bb
> poodle255-kernel-2.4-embedix.bb
> poodle-kernel-2.4-embedix.bb
> shepherd-kernel-2.4-embedix.bb
> openzaurus-pxa27x_2.4.20-rmk2-embedix20050602.bb
> openzaurus-sa_2.4.18-rmk7-pxa3-embedix20030509.bb

IMO kernel recipes should set COMPATIBLE_MACHINE to the machines they 
support and in the case of ARM 2.4 kernels also COMPATIBLE_HOST to stop 
them being selected for EABI targets.

Also bitbake trunk and bitbake-1.8 should have some fixes for 
tryaltconfig, but the kernel recipes need to get fixed first.

regards,

Koen

Re: Broken kernel recipes

[Tom Rini]

On Sun, Dec 07, 2008 at 12:34:17PM +0100, Koen Kooi wrote:
> On 07-12-08 03:11, Tom Rini wrote:
>> Hello,
>>
>> As part of testing meta-toolchain-sbox builds on different arches, I
>> found that sbrsh, on ARM, brings in both the 2.6 kernel for the MACHINE
>> in question, as well as a 2.4 kernel.  In the case of the 2.4 kernel, it
>> first picks up poodle-kernel-2.4-embedix.bb on nokia800, which doesn't
>> work as it wants gcc-2.95, which doesn't exist.  Can I move the
>> following support to packages/obsolete/linux/ ?
>> corgi-kernel-2.4-embedix.bb
>> husky-kernel-2.4-embedix.bb
>> openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.bb
>> poodle255-kernel-2.4-embedix.bb
>> poodle-kernel-2.4-embedix.bb
>> shepherd-kernel-2.4-embedix.bb
>> openzaurus-pxa27x_2.4.20-rmk2-embedix20050602.bb
>> openzaurus-sa_2.4.18-rmk7-pxa3-embedix20030509.bb
>
> IMO kernel recipes should set COMPATIBLE_MACHINE to the machines they  
> support and in the case of ARM 2.4 kernels also COMPATIBLE_HOST to stop  
> them being selected for EABI targets.

In the case of MACHINE=nokia800 and me getting
poodle-kernel-2.4-embedix.bb, that should be the case already?
$ grep COMPAT poodle-kernel-2.4-embedix.bb
openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.inc
poodle-kernel-2.4-embedix.bb:COMPATIBLE_HOST = "arm.*-linux"
openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.inc:COMPATIBLE_MACHINE =
"(poodle|corgi|shepherd|husky|poodle255|tosa)"
openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.inc:COMPATIBLE_HOST =
"arm.*-linux"
openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.inc:COMPATIBLE_MACHINE =
'(c7x0|corgi|husky|shepherd|poodle|poodle255)'

> Also bitbake trunk and bitbake-1.8 should have some fixes for  
> tryaltconfig, but the kernel recipes need to get fixed first.

Can you explain a little more here or point to an example of fixing this
elsewhere?  Thanks!

-- 
Tom Rini

Re: Broken kernel recipes

[Tom Rini]

On Sun, Dec 07, 2008 at 10:57:35AM +0000, Richard Purdie wrote:
> On Sat, 2008-12-06 at 19:11 -0700, Tom Rini wrote:
> > As part of testing meta-toolchain-sbox builds on different arches, I
> > found that sbrsh, on ARM, brings in both the 2.6 kernel for the MACHINE
> > in question, as well as a 2.4 kernel.  In the case of the 2.4 kernel, it
> > first picks up poodle-kernel-2.4-embedix.bb on nokia800, which doesn't
> > work as it wants gcc-2.95, which doesn't exist.  Can I move the
> > following support to packages/obsolete/linux/ ?
> > corgi-kernel-2.4-embedix.bb
> > husky-kernel-2.4-embedix.bb
> > openzaurus-pxa_2.4.18-rmk7-pxa3-embedix20031107.bb
> > poodle255-kernel-2.4-embedix.bb
> > poodle-kernel-2.4-embedix.bb
> > shepherd-kernel-2.4-embedix.bb
> > openzaurus-pxa27x_2.4.20-rmk2-embedix20050602.bb
> > openzaurus-sa_2.4.18-rmk7-pxa3-embedix20030509.bb
> 
> These are needed for sharprom-compat. The more interesting question is
> why they were being brought in - the 2.6 version should provide
> everything they do and have preference?

What's over in http://bugs.openembedded.net/attachment.cgi?id=13197
matches what I was seeing (search for "NOTE: selecting linux-rp to
satisfy virtual/kernel due to PREFERRED_PROVIDERS").  The 2.6 recipe
gets picked as expected, then bitbake adds in the 2.4 recipe too.  I was
seeing this with up to date bitbake-1.8 svn.

> 
> Cheers,
> 
> Richard
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
Tom Rini