* TUNE_FEATURES not reported correctly in pre-build summary
@ 2012-07-20 7:08 Koen Kooi
2012-07-20 16:31 ` Richard Purdie
0 siblings, 1 reply; 3+ messages in thread
From: Koen Kooi @ 2012-07-20 7:08 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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@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@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@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?
regards,
Koen
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: TUNE_FEATURES not reported correctly in pre-build summary
2012-07-20 7:08 TUNE_FEATURES not reported correctly in pre-build summary Koen Kooi
@ 2012-07-20 16:31 ` Richard Purdie
2012-07-20 20:53 ` Koen Kooi
0 siblings, 1 reply; 3+ messages in thread
From: Richard Purdie @ 2012-07-20 16:31 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
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@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@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@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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: TUNE_FEATURES not reported correctly in pre-build summary
2012-07-20 16:31 ` Richard Purdie
@ 2012-07-20 20:53 ` Koen Kooi
0 siblings, 0 replies; 3+ messages in thread
From: Koen Kooi @ 2012-07-20 20:53 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Op 20 jul. 2012, om 18:31 heeft Richard Purdie het volgende geschreven:
> 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@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@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@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?
From memory, the router on the other end crashed: DEFAULTTUNE_beaglebone = "cortexa8hf" in local.conf
regards,
Koen
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-07-20 21:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-20 7:08 TUNE_FEATURES not reported correctly in pre-build summary Koen Kooi
2012-07-20 16:31 ` Richard Purdie
2012-07-20 20:53 ` Koen Kooi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.