Bug 5340

Summary: [ADT] cannot configure CVS project using adt with mips and ppc
Product: [Yocto Project Subprojects] ADT Reporter: Alexandru Georgescu <alexandru.c.georgescu>
Component: adtAssignee: Richard Purdie <richard.purdie>
Status: VERIFIED FIXED QA Contact:
Severity: major    
Priority: High CC: elizabeth.flanagan, jessica.zhang, poky.adt.watcher, poky.watcher, sgw, yi.zhao
Version: 1.5   
Target Milestone: 1.5 M5   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
config.log error none

Description Alexandru Georgescu 2013-10-11 16:06:44 UTC 
Created attachment 1558 [details]
config.log error

poky commit:102bf5e0f640fe85068452a42b85077f1c81e0c9


adt-installer:http://autobuilder.yoctoproject.org/pub/releases/dora-10.0.0/adt-installer-QA/adt_installer.tar.bz2


Cannot do configure on CVS for qemuppc or qemumips (on arm, x86 and x86-64 works fine):

tester@tester-t:~/_work/final/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$ source /opt/poky/1.5/environment-setup-ppc7400-poky-linux 
tester@tester-t:~/_work/final/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@tester-t:~/_work/final/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$ 



NOTE:

May be due to the fact that PATH is not configured correctly. In environment file I have the following PATH setup:
export PATH=/opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/bin:/opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/bin/ppc7400-poky-linux:$PATH


If  searching for the file I cannot find it: 

tester@tester-t:~/_work/final/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$ ll /opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/bin/ppc7400-poky-linux 
ls: cannot access /opt/poky/1.5/sysroots/x86_64-pokysdk-linux/usr/bin/ppc7400-poky-linux: No such file or directory
tester@tester-t:~/_work/final/bsp-automatisation-25-FEB/03_COMPILE_TESTS/cvs-1.12.13$
Comment 1 Richard Purdie 2013-10-11 16:21:49 UTC 
I suspect we need:

diff --git a/meta/classes/toolchain-scripts.bbclass b/meta/classes/toolchain-scripts.bbclass
index 8bdb17d..614f1c0 100644
--- a/meta/classes/toolchain-scripts.bbclass
+++ b/meta/classes/toolchain-scripts.bbclass
@@ -103,7 +103,7 @@ toolchain_create_sdk_env_script_for_installer () {
        script=${SDK_OUTPUT}/${SDKPATH}/environment-setup-${multimach_target_sys}
        rm -f $script
        touch $script
-       echo 'export PATH=${SDKPATHNATIVE}${bindir_nativesdk}:${SDKPATHNATIVE}${bindir_nativesdk}/'"${multimach_target_sys}"':$PATH' >> $script
+       echo 'export PATH=${SDKPATHNATIVE}${bindir_nativesdk}:${SDKPATHNATIVE}${bindir_nativesdk}/${TARGET_SYS}:$PATH' >> $script
        echo 'export PKG_CONFIG_SYSROOT_DIR=##SDKTARGETSYSROOT##' >> $script
        echo 'export PKG_CONFIG_PATH=##SDKTARGETSYSROOT##${target_libdir}/pkgconfig' >> $script
        echo 'export CONFIG_SITE=${SDKPATH}/site-config-'"${multimach_target_sys}" >> $script
Comment 2 Jessica 2013-10-11 18:36:06 UTC 
Alex,

Does the stand alone built toolchain work?

THanks,
Jessica
Comment 3 Alexandru Georgescu 2013-10-11 20:51:25 UTC 
(In reply to comment #2)
> Alex,
> 
> Does the stand alone built toolchain work?
> 
> THanks,
> Jessica

Verifying this RIGHT now.
Comment 4 Yi Zhao 2013-10-12 07:54:15 UTC 
(In reply to comment #2)
> Alex,
> 
> Does the stand alone built toolchain work?
> 
> THanks,
> Jessica

The stand alone built toolchain works well.
Comment 5 Alexandru Georgescu 2013-10-12 23:48:16 UTC 
(In reply to comment #4)
> (In reply to comment #2)
> > Alex,
> > 
> > Does the stand alone built toolchain work?
> > 
> > THanks,
> > Jessica
> 
> The stand alone built toolchain works well.

Thanks Yi for confirming. It seems that my confirmation comment didn't make into Bugzilla.
Comment 6 Alexandru Georgescu 2013-10-13 13:53:42 UTC 
Just retested with http://autobuilder.yoctoproject.org/pub/releases/dora-10.0.0.final/adt-installer-QA/.

The issue is fixed, but there's a little problem on AB for mips. The images are created in an extra qemumips folder: http://adtrepo-dev.yoctoproject.org/1.5-cb2836fee444bf5f7bd74d0612a4cd8f1b5d2e89-dora/rootfs/qemumips/qemumips/ which should be: http://adtrepo-dev.yoctoproject.org/1.5-cb2836fee444bf5f7bd74d0612a4cd8f1b5d2e89-dora/rootfs/qemumips/. 

This causes the ADT installation to fail for mips. Moving the images to the latter folder should fix the issue.
Comment 8 Alexandru Georgescu 2013-10-31 14:56:32 UTC 
The issue was fixed and was retested on the last RC for 1.5.