From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Broken kernel recipes
Date: Sun, 07 Dec 2008 12:34:17 +0100 [thread overview]
Message-ID: <ghgcbq$9of$1@ger.gmane.org> (raw)
In-Reply-To: <20081207021144.GL16628@smtp.west.cox.net>
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
next prev parent reply other threads:[~2008-12-07 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-07 2:11 Broken kernel recipes Tom Rini
2008-12-07 10:48 ` Andrea Adami
2008-12-07 10:57 ` Richard Purdie
2008-12-07 19:23 ` Tom Rini
2008-12-07 11:34 ` Koen Kooi [this message]
2008-12-07 18:52 ` Tom Rini
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='ghgcbq$9of$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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.