New ARM error

DISCUSSION Gary Thomas 2 participants 3 messages Nov 28, 2012 – Nov 29, 2012

lore

Share & tools

lore

Gary Thomas

author

2012-11-28 18:27 UTC #0 lore raw

I build for an OMAP4 platform using
DEFAULTTUNE = "cortexa9hf-neon"

This has been working fine, but after updating to the latest master, I'm getting this error

Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH (cortexa9hf-neonhf-vfp-neon). PACKAGE_ARCHS = (all any noarch armv5hf-vfp armv5ehf-vfp armv6hf-vfp armv7ahf-vfp armv7ahf-vfp-neon cobra4430p82)

(I added the print of the expanded PACKAGE_ARCHS for clarity)

I bisected change this to this commit (Poky/Yocto tree):

commit c5b670e4c9f020ed951d5499a888c50b1d703b62

Author: Martin Jansa <[email protected]>
Date:   Tue Oct 2 17:22:00 2012 +0000

arm/arch-arm*: define ARMPKGARCH_tune-* for default tunes

* tune-foo is not valid override, for it to work I had to add ARMPKGARCH = "${ARMPKGARCH_tune-${DEFAULTTUNE}}"
but that doesn't work without value defined for every supported DEFAULTTUNE value, otherwise it's expanded like this TUNE_PKGARCH (${ARMPKGARCH_tune-armv5te}te).

(From OE-Core rev: 31e4f2dee990ee7f5d7491b65565e71d7d580209)

Signed-off-by Martin Jansa <[email protected]>

Signed-off-by Richard Purdie <[email protected]>

Any ideas how I can fix this?

Signature · 4 lines

------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Martin Jansa

2012-11-28 21:56 UTC #1 lore raw

Quoted 24 lines · Gary Thomas

I build for an OMAP4 platform using
DEFAULTTUNE = "cortexa9hf-neon"
This has been working fine, but after updating to the latest master, I'm getting this error
Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH (cortexa9hf-neonhf-vfp-neon). PACKAGE_ARCHS = (all any noarch armv5hf-vfp armv5ehf-vfp armv6hf-vfp armv7ahf-vfp armv7ahf-vfp-neon cobra4430p82)
(I added the print of the expanded PACKAGE_ARCHS for clarity)
I bisected change this to this commit (Poky/Yocto tree):
commit c5b670e4c9f020ed951d5499a888c50b1d703b62
Author: Martin Jansa <[email protected]>
Date:   Tue Oct 2 17:22:00 2012 +0000
arm/arch-arm*: define ARMPKGARCH_tune-* for default tunes
* tune-foo is not valid override, for it to work I had to add ARMPKGARCH = "${ARMPKGARCH_tune-${DEFAULTTUNE}}"
but that doesn't work without value defined for every supported DEFAULTTUNE value, otherwise it's expanded like this TUNE_PKGARCH (${ARMPKGARCH_tune-armv5te}te).

Quoted 6 lines

(From OE-Core rev: 31e4f2dee990ee7f5d7491b65565e71d7d580209)
Signed-off-by Martin Jansa <[email protected]>
Signed-off-by Richard Purdie <[email protected]>
Any ideas how I can fix this?

I've noticed the same problem today and I'm working on fix. No idea why I haven't seen this with my tests done with contrib/jansa/tune2-test branch.

First part of fix is:
http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-fix&id=a63f9cc754b16a9ac35a1952f70960ec118d6b80

Cheers,

Signature · 1 line

Martin 'JaMa' Jansa     jabber: [email protected]

Martin Jansa

2012-11-29 12:17 UTC #2 lore raw

Quoted 30 lines · Martin Jansa

Quoted 29 lines · Gary Thomas
I build for an OMAP4 platform using
DEFAULTTUNE = "cortexa9hf-neon"
This has been working fine, but after updating to the latest master, I'm getting this error
Error, the PACKAGE_ARCHS variable does not contain TUNE_PKGARCH (cortexa9hf-neonhf-vfp-neon). PACKAGE_ARCHS = (all any noarch armv5hf-vfp armv5ehf-vfp armv6hf-vfp armv7ahf-vfp armv7ahf-vfp-neon cobra4430p82)
(I added the print of the expanded PACKAGE_ARCHS for clarity)
I bisected change this to this commit (Poky/Yocto tree):
commit c5b670e4c9f020ed951d5499a888c50b1d703b62
Author: Martin Jansa <[email protected]>
Date:   Tue Oct 2 17:22:00 2012 +0000
arm/arch-arm*: define ARMPKGARCH_tune-* for default tunes
* tune-foo is not valid override, for it to work I had to add ARMPKGARCH = "${ARMPKGARCH_tune-${DEFAULTTUNE}}"
but that doesn't work without value defined for every supported DEFAULTTUNE value, otherwise it's expanded like this TUNE_PKGARCH (${ARMPKGARCH_tune-armv5te}te).
(From OE-Core rev: 31e4f2dee990ee7f5d7491b65565e71d7d580209)
Signed-off-by Martin Jansa <[email protected]>
Signed-off-by Richard Purdie <[email protected]>

Quoted 8 lines

Quoted 1 line
Any ideas how I can fix this?
I've noticed the same problem today and I'm working on fix. No idea why I haven't seen this with my tests done with contrib/jansa/tune2-test branch.
First part of fix is:
http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/tune-fix&id=a63f9cc754b16a9ac35a1952f70960ec118d6b80

FYI:

I've extended my branch for testing tune files:
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune2-test
to test not only DEFAULTTUNE with fake MACHINES but all combinations of MACHINES and DEFAULTTUNEs.

Script is still running but I've already found some old issues like
1) missing thumb in armv5te-vfp (and higher)
2) little endian PACKAGE_ARCHs included in big endian tunes

And while I was there I've added some possibly usefull tunes like cortexa8t-neon and armv6 without vfp (we had patch for this for almost a year).

I'll send pull request for this branch
http://git.openembedded.org/openembedded-core-contrib/log/?h=jansa/tune-fix
after finishing testing.

I also plan to compare AVAILTUNEs on cortexa9 device with "openssl speed", like hrw did:
http://marcin.juszkiewicz.com.pl/2012/11/28/lets-compare-some-cpu

Cheers,

Signature · 1 line

Martin 'JaMa' Jansa     jabber: [email protected]