Bug 550

Summary: two machines armv4t and armv5te, toolchain problem.
Product: [Build System, Metadata & Runtime] OE-Core Reporter: João Henrique <joaohf>
Component: devtools / tool chainAssignee: Nitin Kamble <nitin.a.kamble>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: ke.yu, kevin.tian, meta.mr.watcher, meta.watcher, richard.purdie, sgw
Version: unspecified   
Target Milestone: 1.0 M3   
Hardware: x86   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description João Henrique 2010-11-28 16:38:48 UTC
Hi,

I am using two machines qemuarm (armv5te) and tsavo530 (my own ARM machine armv4t). The distro is the same. 

I need to run my application on qemuarm and tsavo530.  I need to have two SDKs.

First I compiles the world to use qemuarm and generate the meta-toolchain. It's goes well and the instalation path is: /opt/via/sysroots/x86_64-pokysdk-linux/usr/bin/armv5te-tp-linux-gnueabi/. 

Second I compiles the world to use tsavo530 and generate the meta-toolchain. But the final instalation patch is /opt/via/sysroots/x86_64-pokysdk-linux/usr/bin/armv5te-tp-linux-gnueabi/ not /opt/via/sysroots/x86_64-pokysdk-linux/usr/bin/armv4t-tp-linux-gnueabi/.

Then I clean my build dir (rm -rf build) and compiles world. The meta-toolchain  works like I need.

My question is:

Is any issue in my operation?  I can't figure why. Any hint?

Thanks.
Comment 1 Richard Purdie 2010-12-16 10:02:08 UTC
There were some changes in the way meta-toolchain works in recent versions of the master branch. Could you retry and see if this problem was addressed indirectly by those changes?
Comment 2 João Henrique 2010-12-19 16:27:02 UTC
Hi,

It has solved.

Thanks.