| Summary: | Meet sysroot not found error with scenario2: poky tree mode | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | liping Ke <liping.ke> |
| Component: | core | Assignee: | Scott Garman <scott.a.garman> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, josh, kevin.tian, lianhao.lu, liping.ke, meta.mr.watcher, meta.watcher, sgw, susie.li |
| Version: | 0.9 | ||
| Target Milestone: | 0.9 M4 | ||
| Hardware: | x86 | ||
| OS: | x86 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Program Management | Documentation change: | --- |
|
Description
liping Ke
2010-08-30 19:56:26 UTC
This bug does not exist on top of poky master. I will disable this bug. Thanks! 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 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 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. This bug is verified fixed against my latest build on poky master (c01e8760, Sep 9, Joshua Lock). Thanks& Regards, criping |