Bug 2662

Summary:	Change of ARM tuning is not fully respected
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Marcin Juszkiewicz <marcin>
Component:	configuration	Assignee:	Richard Purdie <richard.purdie>
Status:	VERIFIED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Medium	CC:	sgw, sstncr
Version:	unspecified
Target Milestone:	1.3 M4
Hardware:	x86
OS:	x86_64
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Marcin Juszkiewicz 2012-06-26 10:41:05 UTC

Change of DEFAULTTUNE and ARM_INSTRUCTION_SET ends in change of package arch and triplet from armv7a-vfp-oe-linux-gnueabi to armv7ahf-vfp-neon-oe-linux-gnueabi.
Stamps, work, ipk got changed too but sstate-control uses 'manifest-MACHINE-PN.task' so build fails at do_rootfs (no locale-base-en-us package).

I checked - no such package exists in deploy/ipk/armv7ahf-vfp-neon directory.

At 17:50 I built armv7a-vfp eglibc and then at ~22:50 armv7ahf-vfp-neon one. deploy/ipk has libc* for neon and locale-* for vfp (libc for vfp is absent).

Comment 1 Richard Purdie 2012-09-13 23:18:53 UTC

I tried to reproduce this on master. I build beagboard which uses the armv7a-vfp-neon tuning, then changed DEFAULTTUNE to something else and built armv7ahf-vfp-neon. The builds correctly built.

The fact the sstate manifest uses manifest-MACHINE-PN.task is ok, it will just remove and reinstall things as needed.

So the question is what steps would I follow to produce this? Please reopen if you have more detailed instructions...

Comment 2 Stefan Stanacar 2012-11-02 12:31:37 UTC

Marking as verified.