RFC: unbreaking meta-toolchain naming

[Koen Kooi <k.kooi@student.utwente.nl>]

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

Hi,

Currently meta-toolchain uses TARGET_ARCH as naming which causes a few
problems:

* armv4t/armv5te/armv6 machines will generate identically named
tarballs, while the contents differ. Anyone using static libs will get
SIGILL'ed when trying to run compiled binaries
* ppc405 and ppc603e machines will generate identically named tarballs,
while there is one is softfloat, and the other hardfloat.

The following patch will generate a correctly named tarball on angstrom:

- --- packages/meta/meta-toolchain.bb
6a7cecb31e297844a67f19888a2e7489e81d948c
+++ packages/meta/meta-toolchain.bb
3fe2673a61b591aed4f247f8201896a640d5ed35
@@ -8,6 +8,8 @@ SDK_DEPLOY = "${TMPDIR}/deploy/sdk"
 SDK_OUTPUT = "${SDK_DIR}/image"
 SDK_DEPLOY = "${TMPDIR}/deploy/sdk"

+FEED_ARCH ?= "${TARGET_ARCH}"
+
 IPKG_HOST = "ipkg-cl -f ${IPKGCONF_SDK} -o ${SDK_OUTPUT}"
 IPKG_TARGET = "ipkg-cl -f ${IPKGCONF_TARGET} -o ${SDK_OUTPUT}/${prefix}"

@@ -118,7 +120,7 @@ do_populate_sdk() {
        # package it up
        mkdir -p ${SDK_DEPLOY}
        cd ${SDK_OUTPUT}
- -       fakeroot tar cfj
${SDK_DEPLOY}/${DISTRO}-${DISTRO_VERSION}-${TARGET_ARCH}-${TARGET_OS}-toolchain.tar.bz2
.
+       fakeroot tar cfj
${SDK_DEPLOY}/${DISTRO}-${DISTRO_VERSION}-${FEED_ARCH}-${TARGET_OS}-toolchain.tar.bz2
.
 }

On other distros it will fall back to TARGET_ARCH.

Any objections to applying this?

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)

iD8DBQFHW/QnMkyGM64RGpERAkkSAKCotGh549mm9BDIq149AUkpj+kIyQCaApC1
wPZTQB6Gqt0NFwnPrZjLBco=
=y3cV
-----END PGP SIGNATURE-----