From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Native vs cross confusion
Date: Sat, 15 Dec 2007 11:39:54 +0100 [thread overview]
Message-ID: <4763AEFA.5030707@student.utwente.nl> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
The past few weeks we uncovered a few recipes (qmake2-native,
apache2-native) in OE that are arch specific, but inherit native instead
of cross. The problem with inheriting native.bbclass in such cases makes
the build multimachine unsafe.
There is not one solution for all of them, qmake2 can be fixed by
installing all the spec files or inheriting cross, apache2-native can be
fixed by installing to STAGING_BINDIR_NATIVE or inheriting cross, etc, etc.
This also means that the RFC for uboot-utils needs to get changed, as I
pointed out in my reply to that.
regards,
Koen
- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHY676MkyGM64RGpERApYnAKC4Lt5p1wYDIuAjan10z+HPOmAGAwCeIqul
Fr6KvG7AVu+mRgRtWJxSZVs=
=rkCE
-----END PGP SIGNATURE-----
reply other threads:[~2007-12-15 10:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4763AEFA.5030707@student.utwente.nl \
--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.