From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev linux-linux-headers: add 2.6.22
Date: Sat, 18 Aug 2007 18:56:13 +1000 [thread overview]
Message-ID: <20070818085613.GA28491@twibble.org> (raw)
In-Reply-To: <E1IK9nA-00024I-AJ@linuxtogo.org>
On Sun, Aug 12, 2007 at 07:35:32PM +1000, "koen commit" wrote:
> linux-linux-headers: add 2.6.22
This prompted me try something newer then 2.6.15.99 for my sh4 builds
again. Turn out a "make allnoconfig" gets stuck in an infitinite loop
for sh (looks like it's something to do with no boards being
defined).
Anyway, the following works fine. Is there any particular problem
with doing this?
--- packages/linux-libc-headers/linux-libc-headers_2.6.22.bb 315a90b6e90272ad612070887ceec548917a74d4
+++ packages/linux-libc-headers/linux-libc-headers_2.6.22.bb a6e80aafcd97a39d08120df35a02a98f43221432
@@ -32,7 +32,11 @@ do_configure() {
do_configure() {
set_arch
- oe_runmake allnoconfig ARCH=$ARCH
+ if [ ${ARCH} = "sh" ]; then
+ oe_runmake allyesconfig ARCH=$ARCH
+ else
+ oe_runmake allnoconfig ARCH=$ARCH
+ fi
}
do_compile () {
--
Jamie Lenehan <lenehan@twibble.org>
parent reply other threads:[~2007-08-18 8:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1IK9nA-00024I-AJ@linuxtogo.org>]
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=20070818085613.GA28491@twibble.org \
--to=lenehan@twibble.org \
--cc=openembedded-devel@lists.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.