[meta-freescale] [meta-freescale PATCH v2 1/2] fsl-dynamic-packagearch.bbclass: Stop using ARM-specific architectures

[Otavio Salvador]

On Sat, Oct 8, 2016 at 6:00 AM, Max Krummenacher <max.oss.09 at gmail.com> wrote:
> 2016-09-21 13:16 GMT+02:00 Otavio Salvador <otavio at ossystems.com.br>:
>> The code to dynamically assign the architecture does take into account
>> the default tune so we don't need to include the other architectures
>> with the SoC suffix into the possible package architecture list.
>>
>> This allow for the class to be used across different architectures
>> (such as PowerPC) thus fixing issues while integrating it for QorIQ
>> usage.
>>
>> Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>
>> ---
>>
>
> This does now break certain ARM configurations.
>
> If one configures a build to use thumb by default then the all
> packages which don't explicitly override the instruction set are built
> for thumb and put into the THUMB-SOCARCH while the others are put into
> ARM-SOCARCH.
>
> If not both archs are added to PACKAGE_EXTRA_ARCHS then image creation
> fails because all packages in ARM-SOCARCH are not found.
>
> See also the original patch:
> https://patchwork.openembedded.org/patch/91049/

I see your point.

I think the code will need to have a special case from ARM and behave
different for this architecture while using the simple case as
fallback.

> How can I reproduce the PowerPC use case when preparing a patch?
> I guess just reverting the patch will make someone else unhappy.

You can compare the current PACKAGE_EXTRA_ARCHS output; it cannot change.

The exceptional case for ARM is a bad side effect, indeed. As we don't
use Thumb2 enabled by default it has not been catch in my test.

Please count on me to test and review preliminar patches ;-)

Best Regards,

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750