[OE-core] TUNE_FEATURES not reported correctly in pre-build summary

[Richard Purdie]

On Fri, 2012-07-20 at 09:08 +0200, Koen Kooi wrote:
> Hi,
> 
> I've been experimenting with hardfloat in oe-core (all the previous hf angstrom builds were still using oe-classic) and I noticed that the build summary at the start is incorrect:
> 
> [koen at revo Angstrom]$ MACHINE=beaglebone bitbake -u knotty2 bash
> [..]
> Build Configuration:
> BB_VERSION        = "1.15.3"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "beaglebone"
> DISTRO            = "angstrom"
> DISTRO_VERSION    = "v2012.07-core"
> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
> TARGET_FPU        = "vfp-neon"
> 
> [koen at revo Angstrom]$ MACHINE=beaglebone bitbake -u knotty2 bash -e | grep TUNE_FEATURES\=
> # TUNE_FEATURES=${TUNE_FEATURES_tune-${DEFAULTTUNE}}
> TUNE_FEATURES="armv7a vfp neon callconvention-hard cortexa8"
> 
> It does seem to build the right things:
> 
> [koen at revo Angstrom]$ dpkg-deb -c build/tmp-angstrom_v2012_x-eglibc/deploy/ipk/armv7ahf-vfp-neon/libc6_2.15-r12+svnr19294_armv7ahf-vfp-neon.ipk  | grep hf
> lrwxrwxrwx root/root         0 2012-07-20 03:22 ./lib/ld-linux-armhf.so.3 -> ld-2.15.so
> 
> So why is TUNE_FEATURES not reported correctly in the build banner?

Good question. How are you selecting callconvention-hard?

Cheers,

Richard