[poky] fido: problems with arm926ejs DEFAULTTUNE

[Bryan Evenson]

Martin,

That fixed it.  I can complete a build now.

Thanks,
Bryan

From: Martin Jansa [mailto:martin.jansa at gmail.com]
Sent: Tuesday, November 29, 2016 2:02 PM
To: Bryan Evenson <bevenson at melinkcorp.com>
Cc: poky at yoctoproject.org
Subject: Re: [poky] fido: problems with arm926ejs DEFAULTTUNE

See oe-core commit dbd7fd1cbbc3e7003a48542642acdc80dca3f514

On Tue, Nov 29, 2016 at 5:26 PM, Bryan Evenson <bevenson at melinkcorp.com<mailto:bevenson at melinkcorp.com>> wrote:

> -----Original Message-----
> From: poky-bounces at yoctoproject.org<mailto:poky-bounces at yoctoproject.org> [mailto:poky-<mailto:poky->
> bounces at yoctoproject.org<mailto:bounces at yoctoproject.org>] On Behalf Of Bryan Evenson
> Sent: Wednesday, November 09, 2016 1:29 PM
> To: poky at yoctoproject.org<mailto:poky at yoctoproject.org>
> Subject: [poky] fido: problems with arm926ejs DEFAULTTUNE
>
> I am on poky/dizzy (version 1.7.3) and I am in the process of upgrading my
> build to fido (current HEAD).  I am using the meta-atmel layer to build an
> image for an AT91SAM9G25 using the at91sam9x5ek machine.  When I try to
> build my image using poky/fido, I get the following error:
>
> 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
> (arm926ejse).
>
> In my distro configuration I set DEFAULTTUNE = "arm926ejs".  If I remove this
> line, my image builds but the arch gets set as "armv5e".  The change in arch
> would cause problems for firmware upgrades, as I don't think I'd be able to
> upgrade existing systems when the packages are built for a different arch.
>
> I also noticed that the error message states TUNE_PKGARCH is set to
> "arm926ejse".  I cannot find anywhere in any of the layers I am using where
> "arm926ejse" comes from.  I can find "arm926ejs" and "arm926ejste" but not
> "arm92ejse".
>
> Any thoughts as to what may be going wrong with my build?
I bisected poky and I found that my problem starts after this commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=fido&id=fe66853cded794a7585ed28c519b32930979c2bc.  This commit was actually on master prior to the first fido release.  After this commit (up to current fido HEAD), when I have DEFAULTTUNE = "arm926ejs" then TUNE_PKGARCH gets set as 'arm926ejse'.  Prior to that commit, TUNE_PKGARCH was being set as 'arm926ejste'.  So after that commit, the build tools no longer recognize that my processor is an ARM Thumb processor.

Steps to reproduce:

Here is my autobuilder file for the build I've been testing:

[nightly-atmel-demo-fido]
builders: 'builder1'
repos: [{'poky':
            {'repourl':'git://git.yoctoproject.org/poky.git<http://git.yoctoproject.org/poky.git>',
                 'layerversion':{'core':'meta', 'yoctobsp':'meta-yocto-bsp'},
             'branch':'fido'}},
        {'meta-atmel':
            {'repourl':'git://github.com/linux4sam/meta-atmel.git<http://github.com/linux4sam/meta-atmel.git>',
             'branch':'fido'}},
        {'meta-openembedded':
            {'repourl':'git://git.openembedded.org/meta-openembedded.git<http://git.openembedded.org/meta-openembedded.git>',
             'branch':'fido'}},
        {'meta-qt5':
            {'repourl':'git://github.com/meta-qt5/meta-qt5.git<http://github.com/meta-qt5/meta-qt5.git>',
             'branch':'fido'}}]
steps: [{'SetDest':{}},
        {'CheckOutLayers': {}},
        {'RunPreamble': {}},
        {'GetDistroVersion' : {'distro': 'poky'}},
        {'CreateAutoConf': {'machine': 'at91sam9x5ek', 'SDKMACHINE': 'i686', 'distro': 'poky', 'buildhistory': True, 'packages': 'ipk', 'atextappend': 'EXTRA_IMAGE_FEATURES = ""\nDEFAULTTUNE = "arm926ejs"\n'}},
        {'CreateBBLayersConf': {'buildprovider' : 'yocto', 'layerdirs':
            ['meta-atmel', 'meta-qt5', 'meta-openembedded/meta-oe', 'meta-openembedded/meta-networking', 'meta-openembedded/meta-python']}},
        {'BuildImages': {'images': 'atmel-demo-image'}},
        {'SyncPersistDB' : {'commit' : True, 'distro':'poky'}},
        {'PublishLayerTarballs':{}},
        {'PublishArtifacts': {'artifacts': ['at91sam9x5ek', 'ipk']}}]
scheduler: [{'nightly-scheduler-atmel-fido' :
                {'type':'Nightly',
                 'hour':'1',
                 'minute':'15',}}]

If I build with these settings, I'll get the error I previously mentioned.  If on poky I go back to commit dfa83e662511e8d9f397d458b6eae1bf323cb271, then it builds without errors and builds with ARM Thumb support.  Note that this commit is earlier than the one that caused the Thumb/no Thumb problem, but it was in a set that was committed on that same day; I had to go to a commit prior to that day due to some other unrelated build errors that were introduced by not pulling commits that were dependent on each other.

So is feature-arm-thumb.inc still not recognizing something if DEFAULTTUNE = arm926ejs, or was this working before when it really shouldn't have worked?  Is there something else that I should do to set the correct tune settings for my processor?

Thanks,
Bryan

>
> Thanks,
> Bryan
> --
> _______________________________________________
> poky mailing list
> poky at yoctoproject.org<mailto:poky at yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/poky
--
_______________________________________________
poky mailing list
poky at yoctoproject.org<mailto:poky at yoctoproject.org>
https://lists.yoctoproject.org/listinfo/poky

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20161129/c604ab08/attachment.html>