Bug 5354

Summary: Incorrect path set for ppc adt in x86 machines
Product: [Yocto Project Subprojects] ADT Reporter: Alexandru Georgescu <alexandru.c.georgescu>
Component: adtAssignee: Richard Purdie <richard.purdie>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium+ CC: alexandru.c.georgescu, jessica.zhang, laurentiu.palcu, poky.adt.watcher, poky.watcher, yi.zhao
Version: 1.5   
Target Milestone: 1.6   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Alexandru Georgescu 2013-10-15 15:20:15 UTC
ADT-installer: http://autobuilder.yoctoproject.org/pub/releases/dora-10.0.0.final/adt-installer-QA/


CVS compile fails on for ppc environment in x86 hosts:


tester@ubuntu:~/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$ source /opt/poky/1.5/environment-setup-ppc7400-poky-linux 
tester@ubuntu:~/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$ uname -a
Linux ubuntu 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:19:42 UTC 2013 i686 i686 i686 GNU/Linux
tester@ubuntu:~/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$ ./configure $CONFIGURE_FLAGS
configure: loading site script /opt/poky/1.5/site-config-ppc7400-poky-linux
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for powerpc-poky-linux-strip... powerpc-poky-linux-strip
checking for prefix by checking for cvs... no
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for powerpc-poky-linux-gcc... powerpc-poky-linux-gcc  -m32 -mhard-float -mcpu=7400 --sysroot=/home/tester/test-yocto/qemuppc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
tester@ubuntu:~/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$


The issue may be due to some wrong links set in $PATH variabile in the environment setup script for ppc:

$ cat /opt/poky/1.5/environment-setup-ppc7400-poky-linux 
export PATH=/opt/poky/1.5/sysroots/i686-pokysdk-linux/usr/bin:/opt/poky/1.5/sysroots/i686-pokysdk-linux/usr/bin/powerpc-poky-linux:$PATH


$ ls /opt/poky/1.5/sysroots/i686-pokysdk-linux/usr/bin/powerpc-poky-linux
ls: cannot access /opt/poky/1.5/sysroots/i686-pokysdk-linux/usr/bin/powerpc-poky-linux: No such file or directory
tester@ubuntu:~/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$
Comment 1 Alexandru Georgescu 2013-10-15 15:26:58 UTC
Just did a brief testing on other arches, and the issue seem to be only for PPC.
Comment 2 Richard Purdie 2013-10-16 10:47:29 UTC
I think there are two powerpc toolchains getting built on the autobuilder, probably due to meta-fsl-ppc. One uses "linux" and the other "linux-gnuspe" as the TARGET_OS. The question is therefore whether they're compatible and how we handle this. We don't see this for arm since we always use linux-gnueabi everywhere.
Comment 3 Richard Purdie 2013-10-17 11:20:54 UTC
So just to be clear, the reason there is a problem in the release artifacts is because meta-fsl-ppc was built after the other powerpc toolchains.

The workaround for this issue is to only build either normal or spe SDK/ADT toolchains but not both in the same build. If both are required, use a separate ADT repo for one of them.

A patch which addresses the problem is in review on the mailing list.
Comment 5 Alexandru Georgescu 2013-12-03 15:08:59 UTC
This should be verified on the next weekly build.
Comment 6 Alexandru Georgescu 2013-12-11 16:30:50 UTC
Verified.