Bug 5952

Summary: ADT-installer: using gcc to build c projects failed under ppc architecture with build 1.4.3(2014-03-06)
Product: [Yocto Project Subprojects] ADT Reporter: Ke Zou <ke.zou>
Component: adtAssignee: Laurentiu Palcu <laurentiu.palcu>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, b40290, bluelightning, elizabeth.flanagan, poky.adt.watcher, poky.watcher, yi.zhao, zhenhua.luo
Version: 1.4.3   
Target Milestone: 1.4.3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Found by QA test)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
project configuration error log none

Description Ke Zou 2014-03-12 08:59:25 UTC 
ADT-INSTALLER location:
http://autobuilder.yoctoproject.org/pub/nightly/20140306-3/adt-installer-QA/

C projects compilation test cases:

https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=479
https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=480
https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=481

Compilation errors encountered after installing ppc toolchain and trying to compile these projects.
This only happens to PPC toolchain, others(mips , arm and x86) are fine.

Piece of log:
configure: loading site script /buildarea/adt-installer-automation/sdk/site-config-ppce500v2-poky-linux-gnuspe
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-gnuspe-strip... powerpc-poky-linux-gnuspe-strip
checking for prefix by checking for cvs... /usr/bin/cvs
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for powerpc-poky-linux-gnuspe-gcc... powerpc-poky-linux-gnuspe-gcc  -m32 -mcpu=8548 -mabi=spe -mspe -mfloat-gprs=double --sysroot=/buildarea/adt-installer-automation/test-yocto/ppc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.


Config.log is also enclosed as attachment. It looks like some library files are missing.

Please note that there's similar bug filed :
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5938
But this one refers to qemux86.
Comment 1 Ke Zou 2014-03-12 09:11:01 UTC 
Created attachment 1809 [details]
project configuration error log
Comment 2 Paul Eggleton 2014-03-12 11:49:44 UTC 
This is after Beth's fix for the ADT building on the autobuilder, is that correct?

Also, I'm no expert either on the ADT or on PowerPC, but the "e500v2" looks like it's using the configuration from a meta-fsl-ppc build. Is it possible things are getting confused between the meta-fsl-ppc builds and the ones for mpc8315e-rdb / qemuppc? Which one should be used for this test?
Comment 3 Ke Zou 2014-03-13 05:37:00 UTC 
Yes this is after Beth's fix.

As for the "e500v2" problem, from my opinion the test procedure doesn't care about the target ARCH. This test only installs cross-compiler with ADT-INSTALLER and
then compiles some simple c/cpp program with it, no matter this is for e500v2
or ppc603e.


(In reply to comment #2)
> This is after Beth's fix for the ADT building on the autobuilder, is that
> correct?
> 
> Also, I'm no expert either on the ADT or on PowerPC, but the "e500v2" looks
> like it's using the configuration from a meta-fsl-ppc build. Is it possible
> things are getting confused between the meta-fsl-ppc builds and the ones for
> mpc8315e-rdb / qemuppc? Which one should be used for this test?
Comment 4 Yi Zhao 2014-03-13 07:33:46 UTC 
(In reply to comment #2)
> This is after Beth's fix for the ADT building on the autobuilder, is that
> correct?
> 
> Also, I'm no expert either on the ADT or on PowerPC, but the "e500v2" looks
> like it's using the configuration from a meta-fsl-ppc build. Is it possible
> things are getting confused between the meta-fsl-ppc builds and the ones for
> mpc8315e-rdb / qemuppc? Which one should be used for this test?

This issue is similar with bug 5039. We should use qemuppc with ppc603e for this test. but the autobuilder copied packages from meta-fsl-ppc to the adt repo.
Nevertheless, as Ke said, it should not fail even use the "e500v2" arch compiler to compile a simple c file. Maybe we need someone from freescale to look this ?
Comment 5 Laurentiu Palcu 2014-04-04 10:25:22 UTC 
This has been fixed in master but the fix is too invasive to be included in 1.4. The workaround is not to build the toolchain for two different machines (qemuarm and beagleboard) and use the same repo.