[OE-core] [PATCH 1/4] base.bbclass: Add compatibility package name mapping handler

Koen Kooi koen at dominion.thruhere.net
Wed Jul 27 15:45:32 UTC 2011


Op 27 jul. 2011, om 16:50 heeft Richard Purdie het volgende geschreven:

> On Wed, 2011-07-27 at 09:44 -0500, Mark Hatle wrote:
>> On 7/27/11 9:29 AM, Richard Purdie wrote:
>>> This means if PKGARCHCOMPAT_ARMV7A is set, "armv7a-vfp-neon" is renamed
>>> to be "armv7a". Other compatibility mappings can be added as needed.
>> 
>> There are multiple armv7 cores without neon...  I think there might even be one
>> or two custom cores w/o VFP.  (Yes I know this violates the core spec from ARM,
>> but people do that all of the time.)
> 
> I know there are but for some distros in OE have established "armv7a"
> with a specific meaning. This gives us some way of merging the tune code
> yet defer fixing those conflicts which can then happen at a time of
> their choosing.
> 
> Its assumed anyone enabling the option knows what it means (which
> Angstrom does and is where the request came from).
> 
> FWIW I have just merged the tune changes and this workaround flag.

I think we might need a armv5e -> armv5te one and a slightly more tricky armv4 -> armv4t.

The armv4t without thumb case is interesting since we do want to use the EABI bx,lr but not other thumb instructions. My main reason for avoiding t1 is that the toolchain is perpetually broken for it. If gcc fixes a bug binutils will introduce a new one. 

regards,

Koen



More information about the Openembedded-core mailing list