Bug 247 - Meet sysroot not found error with scenario2: poky tree mode
Summary: Meet sysroot not found error with scenario2: poky tree mode
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 0.9
Hardware: x86 x86
: Medium normal
Target Milestone: 0.9 M4
Assignee: Scott Garman
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-08-30 19:56 UTC by liping Ke
Modified: 2010-12-21 06:09 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description liping Ke 2010-08-30 19:56:26 UTC
hi, scott, 
I am trying unfs scenario 2, poky tree mode with distro-master. I found when I source either poky_tree/poky-init-build-env or poky_tree/build_x86/tmp/environment-setup-XXXX, then runqemu-nfs <kernel> /home/lke/unfs, it will report:
Error: Unable to locate your native sysroot.
Did you forget to source the Poky environment script?

For scenario 1: /opt/poky mode, it works just fine.

Could you help to have a look ?

Thanks a lot!
criping
Comment 1 liping Ke 2010-08-31 02:16:41 UTC
This bug does not exist on top of poky master. 
I will disable this bug. Thanks!
Comment 2 liping Ke 2010-08-31 20:23:42 UTC
I still continuously meet the problem with latest poky master. 
Scott, 
could you help to give me some clue on it?

Thanks a lot!

criping
Comment 3 liping Ke 2010-08-31 23:21:26 UTC
Just got some information from Scott, now I can runqemu-nfs with poky mode by source poky-init-build-env build_x86. Thanks a lot!
Just have one another question for this, could it be possible that we also source build_x86/tmp/environment_setupXXX file, provide similar way as SDK_root mode (scenario 1)?

Thanks a lot!

criping
Comment 4 Joshua Lock - Disabled 2010-09-08 03:28:55 UTC
This was fixed with 9b800fe261650e4300795ce9762422d93cd31251:

scripts: use the exported POKY_NATIVE_SYSROOT variable

Rather than trying to determine things through guess-work use the newly
exported variables to determine where the native binaries reside and
whether we are running in a build directory or not.

Sorry, hand't realised there was a bug open for it.
Comment 5 liping Ke 2010-09-12 21:56:42 UTC
This bug is verified fixed against my latest build on poky master (c01e8760, Sep 9, Joshua Lock).

Thanks& Regards,
criping