ADT_installer location: http://autobuilder.yoctoproject.org/pub/nightly/20130625-2/adt-installer-QA/ ADT repo: http://adtrepo-dev.yoctoproject.org/1.4+snapshot-8e9501ffa8726d69412d669580d787ffedb88d34-master/ git info: master/8e9501ffa8726d69412d669580d787ffedb88d34 Steps: 1. Download adt_installer.tar.bz2 from http://autobuilder.yoctoproject.org/pub/nightly/20130625-2/adt-installer-QA/ 2. Setup the target architecture to arm and install the ADT. 3. After installation finish, I found the environment setting script is environment-setup-armv7a-vfp-neon-poky-linux-gnueabi. It should be environment-setup-armv5te-poky-linux-gnueabi. This file is from package meta-environment-arm_1.0-r8_x86_64-nativesdk.ipk in adt repo. Here is the root cause: Currently on autobuilder, besides nightly-arm (qemuarm), there is an extra layers nightly-fsl-arm (imx53qsb) also build meta-toolchain and the ipk packages will also be copied to adt repo. Although they have the same arch, the core cpu of target machine is different. Unfortunately, when generate the meta-environment-arm package, they have the same package name. So when copy the package to adt repo, the latest one will cover the previous one. The adt_installer and its repo are only for yocto, so we shouldn't copy packages from other extra meta layers(e.g. nightly-fsl-arm or nightly-fsl-ppc) to the adt repo. Otherwise the adt repo will be contaminated. There is a similar issue for toolchain tarball. See bug 4618.
For 20130710-1 build, besides arm, ppc target arch environment setting scripts also be changed in i686 host. It should be "environment-setup-ppc603e-poky-linux", but now it is "environment-setup-ppce500v2-poky-linux-gnuspe". It is because some packages from nightly-fsl-ppc covered the correct packages. ADT repo: http://adtrepo-dev.yoctoproject.org/1.4+snapshot-a63229917a5708de2d161aba0d67168ce0da6365-master/
Hi, This issue still happens on recent builds. Do we have any solution ?
Hi Laurentiu, Please fix this at the beginning of M5 Thanks, Jessica
I've got a fix for this already (http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=lpalcu/b4783_target_arch_change) but it impacts ADT installer: YOCTOADT_TARGETS variable in adt-installer.conf would have to be set to 'armv5te' (for qemuarm toolchain) or 'armv7a-vfp-neon' (for beagleboard) instead of just 'arm' as it is right now. This would be needed for all architectures. The alternative is for the user to use the machine name: beagleboard or qemuarm. Even though this would be easier, from the user perspective, it's not ideal. The user might also have to choose from a lot of machine names. The easiest way, from the user point of view, is to have just 'x86', 'arm', etc. Unfortunately, I'm not sure we can achieve that any time soon, at least not in this release cycle. I'll continue my investigations though and see if I can come up with a better solution for the time being.
I think we should merge the TUNE_PKGARCH patches and add comments to the configuration file showing the defaults for our standard machine set (qemu and meta-yocto-bsp machines). Would that approach work?
That can be done, of course. I'll do the changes and make some tests locally.
Patches sent on the oe-core ML.
Patches merged: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=bd0fc8e8927fb5d5ec4fb080b3f0d7b1b19b4583 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5d125f514fc2ecb00e1a8a1079d279db2d42895f http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=9d3d1a2da2a804c74ff11a618e69add0d64a555d http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=32090b6ea0bf7d49a6c8bfb271535c644fe612d6 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=5992830145c55f5103b4ba24f98eeeae13c604fc
Verified with 1.5 M5 rc4. poky master: 853bc53cd58a621918f0e5ce662dba263d1befb4