All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Broken kernel recipes
Date: Sun, 07 Dec 2008 10:57:35 +0000	[thread overview]
Message-ID: <1228647455.5427.0.camel@dax.rpnet.com> (raw)
In-Reply-To: <20081207021144.GL16628@smtp.west.cox.net>

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




  parent reply	other threads:[~2008-12-07 11:01 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 [this message]
2008-12-07 19:23   ` Tom Rini
2008-12-07 11:34 ` Koen Kooi
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=1228647455.5427.0.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --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.