meta-linaro and toolchain-layer

[Khem Raj <raj.khem@gmail.com>]

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

Hi,

Ken Werner @ Linaro has created a meta-linaro layer. I have created a
github repo of same here https://github.com/kraj/meta-linaro

Moving forward soon gcc 4.7 will land in OE-Core and 4.6 will be
more or less retired. In natural progression it would move to
toolchain-layer if there are consumers of it.

linaro is also working on gcc-4.7 improvements in  same manner as
4.6  and there could be more tools e.g. gdb binutils etc. that could
be useful for armv7+ from that layer.

I would like to propose few things we could do.

Use gcc-4.6 from meta-linaro and retire it from toolchain-layer
which means toolchain layer only has gcc-4.5 and eventually
This also means that we don't move gcc-4.6 into toolchain-layer
when its relegated from OE-Core

In similar fashion add recipes for gcc-linaro-4.7 whenever linaro
makes first 4.7 based release

Does anybody see downsides to this approach ?

This could mean that distro may have multiple compilers for different
architectures e.g. linaro toolchain for arm
architecture and may be OE-Core provided toolchain for rest of them

another option is that we do the same thing where we cherry-pick
linaro patches into toolchain-layer and append them on top gcc from
OE-Core which we have been doing with 4.6 it does mean extra work
validation and maintenance that I would like to avoid.

Thanks

- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+ArNYACgkQuwUzVZGdMxQ1gACeNBUacwHJrvYuzpStJKeVZHb6
4qUAniohGmPBRhVJJtjEpGlG/JyKdCvt
=fnnP
-----END PGP SIGNATURE-----