4169 2013-04-02 02:57:33 +0000 [Autobuilder] arm toochain sdk: target arch change from armv5te to armv7a-vfp-neon 2013-04-04 18:32:18 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 1.4 x86 Multiple RESOLVED FIXED Medium+ normal 1.4 M6 1 yi.zhao elizabeth.flanagan elizabeth.flanagan infras.ab.watcher Infras.watcher jessica.zhang laurentiu.palcu ning.zhang richard.purdie --- --- --- oldest_to_newest 31334 0 yi.zhao 2013-04-02 02:57:33 +0000 Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130327-1/toolchain/ Git rev: 1.4_M5/bdca49274173153b1b0a72887de6321b4756b684 For the arm toolchain sdk, I found the target arch changed from armv5te to armv7a-vfp-neno . When I install the poky-eglibc-x86_64-arm-toolchain-gmae-1.3+snapshot-20130327.sh, the target arch is armv7a-vfp-neon: ############# $ ls /opt/poky/1.3+snapshot/ environment-setup-armv7a-vfp-neon-poky-linux-gnueabi site-config-armv7a-vfp-neon-poky-linux-gnueabi sysroots version-armv7a-vfp-neon-poky-linux-gnueabi ############# But for previous arm toolchain sdk, the target arch is armv5te: ############# $ ls /opt/poky/1.3+snapshot/ environment-setup-armv5te-poky-linux-gnueabi site-config-armv5te-poky-linux-gnueabi sysroots version-armv5te-poky-linux-gnueabi ############# This is caused by MACHINE setting. If the MACHINE is qemuarm, the target arch would be armv5te. If the MACHINE is beagleboard, the target arch would be beagleboard. I think we should changed the arch to armv5te, in order to be compatible with the adt_installer. 31562 1 elizabeth.flanagan 2013-04-04 18:32:18 +0000 As of http://autobuilder.yoctoproject.org/pub/nightly/20130404-2 eflanagan@envy ~/Downloads $ ls /opt/poky/1.3+snapshot/ environment-setup-armv5te-poky-linux-gnueabi site-config-armv5te-poky-linux-gnueabi sysroots/ version-armv5te-poky-linux-gnueabi