From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: mtn disapprove
Date: Fri, 11 Jan 2008 19:48:32 +0100 [thread overview]
Message-ID: <fm8dm0$ikl$1@ger.gmane.org> (raw)
In-Reply-To: <fm86uh$qa8$1@ger.gmane.org>
It seems this solution is not yet perfect. All of the sudden, bitbake
cooks up an armv5te version of libogg for the collie. My suspicion is
that this has to do with PACKAGE_EXTRA_ARCHS.
What does PACKAGE_EXTRA_ARCHS do? If set to "armv4 armv4t armv5e
armv5te", can that provide problems for a device like the collie which
is arm-only, not armv5te? How about the poodle? Is that device and all
other Zaurus safe with "armv4 armv4t armv5e armv5te"?
If my suspicion is true, my suggestion for Zaurus-2.6.inc is
-PACKAGE_EXTRA_ARCHS = "armv4 armv4t armv5e armv5te"
+PACKAGE_EXTRA_ARCHS ?= "armv4 armv4t armv5e armv5te"
+PACKAGE_EXTRA_ARCHS_collie = ""
next prev parent reply other threads:[~2008-01-11 18:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 7:36 mtn disapprove Koen Kooi
2008-01-11 8:30 ` Rolf Leggewie
2008-01-11 8:38 ` Koen Kooi
2008-01-11 16:53 ` Rolf Leggewie
2008-01-11 18:48 ` Rolf Leggewie [this message]
2008-01-11 19:20 ` Koen Kooi
2008-01-11 19:32 ` Rolf Leggewie
2008-01-11 23:22 ` Thomas Kunze
2008-01-12 10:39 ` Rolf Leggewie
2008-01-13 13:09 ` Thomas Kunze
2008-01-13 15:06 ` Rolf Leggewie
2008-01-13 16:30 ` Koen Kooi
2008-01-14 11:21 ` Florian Boor
2008-01-14 11:44 ` Rolf Leggewie
2008-01-11 19:36 ` Rolf Leggewie
2008-01-11 11:06 ` ohviey1
-- strict thread matches above, loose matches on Subject: below --
2008-01-11 20:57 QMan
2008-01-12 10:42 ` Rolf Leggewie
2008-01-12 11:41 ` Richard Purdie
2008-01-13 20:26 QMan
2008-01-28 13:51 ` Rolf Leggewie
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='fm8dm0$ikl$1@ger.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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.