[Angstrom-devel] how to handle non-standard toolchains

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

There are some archs in OE that require a non-standard toolchain to build. E.g. avr32
needs a patch to gcc that is sooooo evil[1] that it needs a seperate arv32-gcc recipe, and
blackfin requires a gcc from some svn repo, so that is another seperate recipe. How should
 we integrate those into angstrom distro versions? For historical reasons a distro version
('release') has meant 'this specific toolchain', and so far most archs behave nicely with
the same toolchain (e.g gcc 4.1.2/binutils 2.18/glibc 2.6), but some archs are stuck with
gcc 4.1.1 (e.g. ppc-nofpu).

Thoughts? Commments? Solutions?

regards,

Koen

[1] http://dominion.kabel.utwente.nl/koen/cms/fun-with-vendor-patches
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHFKYnMkyGM64RGpERAvVkAJ9+F1BF7Dg3lTyPOPgMPqnVWkDh/QCeNPhe
aLWKuhIfcI4NRV5SdEepq88=
=xvDs
-----END PGP SIGNATURE-----