Bug 6906

Summary: [1.6.2] C++ compiler does not work for ppce500v2 cross toolchain
Product: [Yocto Project Subprojects] ADT Reporter: Yi Zhao <yi.zhao>
Component: adtAssignee: Saul Wold <sgw>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, ke.zou, poky.adt.watcher, poky.watcher, richard.purdie, zhangle.yang
Version: 1.6.2   
Target Milestone: 1.6.2   
Hardware: x86   
OS: ppc   
Whiteboard: Relaase Note
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
sudoku compile log none

Description Yi Zhao 2014-10-29 09:02:49 UTC 
Created attachment 2220 [details]
sudoku compile log

Toolchain location: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.6.2.rc1/toolchain/x86_64/poky-eglibc-x86_64-core-image-sato-ppce500v2-toolchain-1.6.1.sh

Git rev: daisy/313864bf528696a72c3ee6b3dec1a0c7b0b223f6 

The ppce500v2 toolchain is from meta-fsl-ppc layer. This issue is same with bug 6613 which already fixed in 1.7.

When compile sudoku-savant, I got the following error:
##########################
In file included from main.cpp:10:0:
/opt/poky/1.6.1/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/cstdlib:41:28: fatal error: bits/c++config.h: No such file or directory
 #include <bits/c++config.h>
                            ^
compilation terminated.
In file included from utils.cpp:1:0:
/opt/poky/1.6.1/sysroots/ppce500v2-poky-linux-gnuspe/usr/include/c++/cctype:41:28: fatal error: bits/c++config.h: No such file or directory
 #include <bits/c++config.h>
                            ^
compilation terminated.
make[2]: *** [main.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [utils.o] Error 1
make[2]: Leaving directory `/buildarea1/sdk-automation-test/test_files/sudoku-savant-1.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/buildarea1/sdk-automation-test/test_files/sudoku-savant-1.3'
make: *** [all] Error 2
#############################

The attachment is the full build log.
Comment 1 Richard Purdie 2014-10-30 15:08:49 UTC 
My big concern with this bug is that the changes to fix this are fairly invasive. I'd therefore prefer not to try and fix this in 1.6.2 but direct people to 1.7 for this toolchain.