Bug 1367

Summary: runqemu-extract-sdk built with meta-toolchain is unable to extract rootfs
Product: [Yocto Project Subprojects] ADT Reporter: Jessica <jessica.zhang>
Component: kernel analysisAssignee: Scott Garman <scott.a.garman>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Medium CC: yp.sdk.watcher, yp.watcher
Version: unspecified   
Target Milestone: 1.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Jessica 2011-08-11 16:48:42 UTC 
build meta-toolchain against latest poky master, after extract it under /opt/poky, source the environment setup script.  Then using runqemu-extract-sdk to extract a rootfs, noticed the following issues:

1. /opt/poky/1.0+snapshot/sysroots/i686-pokysdk-linux/usr/bin/pseudo is no longer executable, after fixing that, I'm getting the following
2. opt/poky/1.0+snapshot/sysroots/i686-pokysdk-linux/usr/bin/runqemu-extract-sdk: line 89: /opt/poky/1.0+snapshot/sysroots/i686-pokysdk-linux/usr/bin/pseudo: No such file or directory

BTW, the runqemu-extract-sdk works fine under poky tree mode, which through bitbake meta-ide-support
Comment 1 Scott Garman 2011-08-11 20:29:17 UTC 
Jessica,

I am not able to reproduce this after building my own meta-toolchain. 

Notably, when I extract the meta-toolchain tarball into /opt/poky, my pseudo binary exists and is executable. This tells me that perhaps something is wrong with the meta-toolchain tarball or the way you extracted it. Can you reproduce this from a new build of meta-toolchain?

Another thing to verify is your OS architecture. The uname -a command should show whether your kernel is i686 or x86_64. If that reports you're running an x86_64 kernel, then your meta-toolchain tarball was built for the wrong architecture.
Comment 2 Jessica 2011-08-11 21:35:00 UTC 
Scott,

Thanks for checking things out.   I've used "sudo tar -xvjf <toolchain.tarball> ." under / to extracted my toolchain, is it different from how you did yours? BTW, my kernel is i686, so at least the toolchain arch is correct.  I'm surprised to hear that your pseudo is executable where mine's not.
I'll rebuilt a meta-toolchain to see whether that will make things different.
Comment 3 Scott Garman 2011-08-12 08:05:05 UTC 
Also, check your umask setting (just run "umask"). It should be set to 0022. If it's set to something else, that can interfere with file persmissions settings when creating new files.
Comment 4 Jessica 2011-08-12 09:24:52 UTC 
Scott,

This is due to my corrupted cache, sstate, etc.  after cleaning up my tmpdir and sstate and rebuild toolchain, the problem is gone.  Same symptom as 1356