Bug 179

Summary: when parse netbook environment script, error happens when creating c project
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: liping Ke <liping.ke>
Component: eclipse-pluginAssignee: Jessica <jessica.zhang>
Status: VERIFIED INVALID QA Contact:
Severity: normal    
Priority: Undecided CC: kevin.tian, lianhao.lu, liping.ke, sgw, yongkang.you, yp.ep.watcher, yp.watcher
Version: 0.9   
Target Milestone: 0.9 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Program Management Documentation change: ---

Description liping Ke 2010-08-03 00:03:15 UTC
When create a c yocto project (empty or not), when parsing netbook environment files, it will show messed up CXXFLAGS and CFLAGS under autotools->configure settings->Command. Please help to verify in your environment.

The simple reproduce step is to build a netbook sdk and point to that /opt/poky.

paste environment files in my machine:


export PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/bin:$PATH
export PKG_CONFIG_SYSROOT_DIR=/opt/poky/sysroots/i586-poky-linux
export PKG_CONFIG_PATH=/opt/poky/sysroots/i586-poky-linux/usr/lib/pkgconfig
export CONFIG_SITE=/opt/poky/site-config-i586-poky-linux
export CC=i586-poky-linux-gcc
export CXX=i586-poky-linux-g++
export CONFIGURE_FLAGS="--target=i586-poky-linux --host=i586-poky-linux --build=i586-linux"
export CFLAGS="-m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse"
export CXXFLAGS="-m32 -march=core2 -msse3 -mtune=generic -mfpmath=sse"
alias opkg='LD_LIBRARY_PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/lib /opt/poky/sysroots/i586-pokysdk-linux/usr/bin/opkg-cl -f /opt/poky/sysroots/i586-pokysdk-linux//etc/opkg-sdk.conf -o /opt/poky/sysroots/i586-pokysdk-linux'
alias opkg-target='LD_LIBRARY_PATH=/opt/poky/sysroots/i586-pokysdk-linux/usr/lib /opt/poky/sysroots/i586-pokysdk-linux/usr/bin/opkg-cl -f /opt/poky/sysroots/i586-poky-linux/etc/opkg.conf -o /opt/poky/sysroots/i586-poky-linux'


criping
Comment 1 liping Ke 2010-08-03 00:05:15 UTC
For qemu-x86, everything is just fine.
Comment 2 liping Ke 2010-08-03 00:42:31 UTC
This phenomenon happens because of the old existing legacy yocto projects. When I clear the whole environment, everything is fine. 

Thanks.
criping