[OE-core] fido -> jethro switching problem

Koen Kooi koen at dominion.thruhere.net
Mon Jan 18 12:25:39 UTC 2016


> Op 18 jan. 2016, om 12:55 heeft Steffen Sledz <sledz at dresearch-fe.de> het volgende geschreven:
> 
> On 15.01.2016 15:29, Koen Kooi wrote:
>>> Op 15 jan. 2016 om 15:26 heeft Steffen Sledz <sledz at dresearch-fe.de> het volgende geschreven:
>>>> On 15.01.2016 14:24, Steffen Sledz wrote:
>>>> And I made another interesting discovery: The exception appears on certain machine types only, e.g with qemuarm it appears, with qemuarm64 or qemux86 not.
>>> 
>>> It seems that all machines based on armv5e are affected.
>> 
>> FWIW, I'm seeing the same problem. The last time it happened it was due to the fixup angstrom does for broken arm BSPs
> 
> I've identified this line from meta-angstrom/conf/distro/include/angstrom.inc[1] as "trigger" for the exception in the way, that commenting out this line avoids the exception.
> 
> --------------> snip <----------------
> # Add FEED_ARCH to machine overrides so we get access to e.g. 'armv7a' and 'sh4'
> # Hopefully we'll never see a machine or arch with 'all' as substring
> MACHINEOVERRIDES .= ":${@bb.data.getVar('FEED_ARCH', d,1).replace('all','noarch')}"
> --------------> snip <————————

So that bit doesn’t do what it says it does anymore, this diff after removing it:

-# $MACHINEOVERRIDES [10 operations]
+# $MACHINEOVERRIDES [9 operations]
 #   set? /build/v2015.12/sources/openembedded-core/meta/conf/bitbake.conf:688
 #     "${MACHINE}"
 #   set /build/v2015.12/sources/openembedded-core/meta/conf/bitbake.conf:689
@@ -9106,15 +9106,13 @@
 #     "${@bb.utils.contains("TUNE_FEATURES", "armv5", "armv5:", "" ,d)}"
 #   predot /build/v2015.12/sources/openembedded-core/meta/conf/machine/include/arm/arch-armv4.inc:13
 #     "${@bb.utils.contains("TUNE_FEATURES", "armv4", "armv4:", "" ,d)}"
-#   postdot /build/v2015.12/sources/meta-angstrom/conf/distro/include/angstrom.inc:30
-#     ":${@bb.data.getVar('FEED_ARCH', d,1).replace('all','noarch')}"
 #   append /build/v2015.12/sources/meta-angstrom/conf/distro/include/angstrom-core-tweaks.inc:27
 #     [vardepsexclude] "SOC_FAMILY"
 #   set /build/v2015.12/sources/openembedded-core/meta/conf/documentation.conf:282
 #     [doc] "Lists overrides specific to the current machine. By default, this list includes the value of MACHINE."
 # pre-expansion value:
-#   "${@bb.utils.contains("TUNE_FEATURES", "armv4", "armv4:", "" ,d)}${@bb.utils.contains("TUNE_FEATURES", "armv5", "armv5:", "" ,d)}${@bb.utils.contains("TUNE_FEATURES", "armv6", "armv6:", "" ,d)}${@bb.utils.contains("TUNE_FEATURES", "armv7a", "armv7a:", "" ,d)}${@['', '${SOC_FAMILY}:']['${SOC_FAMILY}' != '']}${MACHINE}:${@bb.data.getVar('FEED_ARCH', d,1).replace('all','noarch')}"
-MACHINEOVERRIDES="armv7a:ti33x:beaglebone:armv7at2hf-vfp-neon"
+#   "${@bb.utils.contains("TUNE_FEATURES", "armv4", "armv4:", "" ,d)}${@bb.utils.contains("TUNE_FEATURES", "armv5", "armv5:", "" ,d)}${@bb.utils.contains("TUNE_FEATURES", "armv6", "armv6:", "" ,d)}${@bb.utils.contains("TUNE_FEATURES", "armv7a", "armv7a:", "" ,d)}${@['', '${SOC_FAMILY}:']['${SOC_FAMILY}' != '']}${MACHINE}"
+MACHINEOVERRIDES=“armv7a:ti33x:beaglebone"

So ‘armv7a’ is already there, 'armv7at2hf-vfp-neon’ isn’t needed since that information is availble from MACHINE_FEATURES already. I’ll drop the bit in jethro and master.

Thanks for tracking this down!

regards,

Koen


More information about the Openembedded-core mailing list