summaryrefslogtreecommitdiff
path: root/meta-rt/images/core-image-minimal-rt.bb
diff options
context:
space:
mode:
authorPhil Blundell <philb@gnu.org>2011-07-29 00:31:15 +0000
committerKhem Raj <raj.khem@gmail.com>2011-07-29 09:47:56 -0700
commit391c0102a81455c76244d13b6878e3a76cca65dc (patch)
tree4da0ce7dd3ab94f4e2c4ef2c127b0ee0d8b38a2d /meta-rt/images/core-image-minimal-rt.bb
parent3b7784021259ac745c80043bec16189fa8f4e45e (diff)
downloadopenembedded-core-391c0102a81455c76244d13b6878e3a76cca65dc.tar.gz
openembedded-core-391c0102a81455c76244d13b6878e3a76cca65dc.tar.bz2
openembedded-core-391c0102a81455c76244d13b6878e3a76cca65dc.tar.xz
openembedded-core-391c0102a81455c76244d13b6878e3a76cca65dc.zip
arch-armv6, arch-armv5-dsp: correct endianness confusion
PACKAGE_EXTRA_ARCHS_tune-armv5eb needs to be defined in terms of the non-e with the same endianness, i.e. PACKAGE_EXTRA_ARCHS_tune-armv5b not PACKAGE_EXTRA_ARCHS_tune-armv5, otherwise PACKAGE_EXTRA_ARCHS will end up containing a semi-random mixture of endiannesses and disaster will ensue. Likewise for the vfp and armv6 variants. This is all a bit confusing because TUNE_FEATURES is done the opposite way around, i.e. TUNE_FEATURES_tune-armv5eb is derived by taking the armv5e version and adding bigendian. But fixing that is probably a subject for a separate patch. Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-rt/images/core-image-minimal-rt.bb')
0 files changed, 0 insertions, 0 deletions