From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: Cleaning up SDK/Toolchain
Date: Thu, 18 Oct 2007 11:39:57 +0200 [thread overview]
Message-ID: <471729ED.9080208@student.utwente.nl> (raw)
In-Reply-To: <4510693243.20071017152524@vanille-media.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael 'Mickey' Lauer schreef:
> On OEDEM we talked about SDK and Toolchain issues. Richard Purdie
> recently merged Poky's meta-toolchain package plus the infrastructure
> that enables OE building external toolchains for usage with or without
> OpenEmbedded.
>
> In order to make this a bit more clean, we'd like to remove some of
> the older meta-sdk packages, if no one objects. If you are still using
> the meta-sdk packages, could you merge them towards using
> meta-toolchain?
>
> Adding custom packages to the meta-toolchain should just be a matter
> of overriding TOOLCHAIN_TARGET_TASK now.
Apart from the libc flaw I pointed out in another mail, the naming of the toolchains is
broken as well:
angstrom-2007.9-test-20071017-arm-linux-gnueabi-toolchain.tar.bz2
angstrom-2007.9-test-20071017-arm-linux-uclibcgnueabi-toolchain.tar.bz2
angstrom-2007.9-test-20071018-powerpc-linux-toolchain.tar.bz2
angstrom-2007.9-test-20071018-powerpc-linux-uclibc-toolchain.tar.bz2
There's no way to see if the arm ones are armv4t, armv5te or armv6 and the powerpc ones
ppc405, ppc440 or ppc603e. For compiling 'hello world' that doesn't matter, but libc6.so
and libgcc_s.so will contain instruction not available on other cpus of that arch (e.g.
clz is not in armv4t), so your binary will probably not work on your device.
My idea is to use PACKAGE_ARCH (e.g. armv5te or ppc603e) instead of TARGET_ARCH.
Comments/hints/ideas?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHFyntMkyGM64RGpERAm+UAJsHn+2oCOjJoHlTxJ0o9SmSTP5bjQCffUcx
fNmkEs0chQ5uAtVAoxOsZ7c=
=gywh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-18 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 13:25 Cleaning up SDK/Toolchain Michael 'Mickey' Lauer
2007-10-18 9:39 ` Koen Kooi [this message]
2007-10-18 11:59 ` Richard Purdie
2007-10-18 13:44 ` Koen Kooi
2007-10-18 17:30 ` Koen Kooi
2007-10-22 11:39 ` Koen Kooi
2007-10-22 14:36 ` Richard Purdie
2007-10-22 15:34 ` Koen Kooi
2007-10-22 16:43 ` Graeme Gregory
2007-10-22 18:24 ` Richard Purdie
2007-10-22 20:46 ` Leon Woestenberg
2007-10-22 21:02 ` Graeme Gregory
2007-10-23 2:33 ` mwester
2007-10-24 20:34 ` Koen Kooi
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=471729ED.9080208@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.