Bug 8491 - runqemu command is not in the $PATH for toolchain ext sdk
Summary: runqemu command is not in the $PATH for toolchain ext sdk
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Paul Eggleton
QA Contact: Yi Zhao
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-10-13 06:20 UTC by Yi Zhao
Modified: 2015-10-16 09:57 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2015-10-13 06:20:17 UTC 
Git rev: jethro/eac61f37e36099f74485dab398b57f3812826d17

Steps:
1. Build a toolchain ext sdk:
   bitbake core-image-sato -c populate_sdk_ext

2. Intall the sdk ext:
   ./poky-glibc-x86_64-core-image-sato-i586-toolchain-ext-2.0.sh

3. Set the environment:
   $ . /buildarea2/poky_sdk/environment-setup-i586-poky-linux
   $ which runqemu
   $

There is no runqemu command in the $PATH, we can not use the toolchain ext to launch pre-build qemu image directly.
Comment 1 Paul Eggleton 2015-10-13 06:40:27 UTC 
This is semi-intentional. Use "devtool runqemu" instead.
Comment 2 Paul Eggleton 2015-10-16 09:57:15 UTC 
We have a means to run QEMU within the ext SDK, it just isn't exactly the same as the traditional SDK. We could add a wrapper script fairly easily but I'm just not sure I see a lot of value in doing that, so I'm marking this as WONTFIX. (When the extensible SDK gets documented, which it isn't currently, we will be covering this so user expectations ought to be set correctly.)