[meta-freescale] [OE-core] trouble related to oe-core update

[Max Krummenacher]

Hi All

Andreas Müller <schnitzeltony at ...> writes:

>
> On Mon, May 18, 2015 at 2:50 PM, Otavio Salvador
> <otavio <at> ossystems.com.br> wrote:
> > On Mon, May 18, 2015 at 9:43 AM, Andreas Müller
> > <schnitzeltony <at> googlemail.com> wrote:
> >> On Mon, May 18, 2015 at 1:55 PM, Otavio Salvador
> >> <otavio <at> ossystems.com.br> wrote:
> >>> On Mon, May 18, 2015 at 6:00 AM, Andreas Müller
> >>> <schnitzeltony <at> googlemail.com> wrote:
> >>>> On Mon, May 18, 2015 at 10:01 AM, Martin Jansa <martin.jansa <at>
gmail.com> wrote:
> >>>>> On Mon, May 18, 2015 at 09:46:03AM +0200, Andreas Müller wrote:

> >>>>>> have seen that a while ago but had no time to take care.
> >>>>>>
> >>>>>> Since oe-core commit
> >>>>>>
> >>>>>> commit 3e760031f91fb87c3e2f62b77a117eb41164f259
> >>>>>> Author: Martin Jansa <martin.jansa <at> gmail.com>
> >>>>>> Date:   Wed Feb 18 15:40:35 2015 +0100
> >>>>>>
> >>>>>>     feature-arm-thumb.inc: respect ARM_INSTRUCTION_SET when adding
thumb suffix
> >>>>>>
> >>>>>> I get
> >>>>>>
> >>>>>> ERROR:  OE-core's config sanity checker detected a potential
misconfiguration.
> >>>>>>     Either fix the cause of this error or at your own risk disable the
> >>>>>> checker (see sanity.conf).
> >>>>>>     Following is the list of potential problems / advisories:
> >>>>>>
> >>>>>>     Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH
> >>>>>> (cortexa9t2hf-vfp-neon).
> >>>>>>
> >>>>>> I don't understand this fully but it seems that
> >>>>>> fsl-dynamic-packagearch.bbclass would add this pkg arch but this never
> >>>>>> happens because sanity.bbclass is executed first and interrupts
> >>>>>> parsing. What I don't understand: Am I the only one having this issue

That is wrong, see below.

> >>>>> I'm not using meta-fsl*, butdo you have this patch in your setup?
> >>>>> http://patches.openembedded.org/patch/90989/
> >>>>> it was discussed off-list a while ago and this change looks like result
> >>>>> of that discussion.
> >>>>>
> >>>> Have meta-fsl-arm current master in my layers. This contains a
similar patch:
> >>>>
> >>>> commit bfe01a0ebde407086f4a7710ea165c6beff310d7
> >>>> Author: Max Krummenacher <max.oss.09 <at> gmail.com>
> >>>> Date:   Mon Mar 30 23:49:32 2015 +0200
> >>>>
> >>>>     fsl-dynamic-packagearch: add all MACHINE_SOCARCH feeds
> >>>>

meta-fsl-arm adds an additional package feed for the SOC ARCH packages
to the ones already available.
e.g. for i.MX6 cortexa9hf-vfp-neon-mx6qdl.

If the configuration sets the default instruction set to thumb
(as angstrom does) then all packages which are built with thumb
are placed in a thumb specific feed.
So meta-fsl-arm must add yet another package feed,
e.g. cortexa9t2hf-vfp-neon-mx6qdl.
The mentioned patch (and its changes due to regressions or
side effects) does this so that during do_rootfs these thumb packages
are actually found.

> >>>> My problem seems to be that sanity.bbclass bails out before code in
> >>>> fsl-dynamic-packagearch.bbclass is executed (and would fix). Playing
> >>>> around with layer priorities / order of layers nothing changed
> >>>> situation.
> >>>

I believe that the way Angstrom configures thumb together with how
meta-fsl-arm sets the DEFAULTTUNE the resulting build does
a) build thumb packages
and
b) does not have thumb in TUNE_FEATURES
which makes the sanity checker kick in.

Standard assignment from Angstrom after some python magic:
DEFAULTTUNE := "${@arm_tune_handler(d)}"
https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/include/arm-defaults.inc#L22
Plus setting the default instruction set to thumb here:
https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/include/angstrom.inc#L56

Override in meta-fsl-arm which takes precedence
https://github.com/Freescale/meta-fsl-arm/blob/master/conf/machine/include/imx-base.inc#L37
DEFAULTTUNE_mx6 ?= "cortexa9hf-neon"


My luck was the following define in the machine configuration
DEFAULTTUNE_mx6 = "armv7athf-neon"
because I build for cortex-a5 and cortex-a9 machines and don't want to
rebuild all packages due to specific machine archs.
http://git.toradex.com/cgit/meta-toradex.git/tree/conf/machine/apalis-imx6.conf?h=V2.4#n6

So you probably get a working configuration when adding one of the
following:
DEFAULTTUNE_mx6 = "armv7athf-neon"
DEFAULTTUNE_mx6 = "cortexa9thf-neon"


Regards
Max