Bug 3968

Summary: an error appear when selecting kernel for yocto-bsp 1.3.1
Product: [Yocto Project Subprojects] Eclipse Plugin Reporter: Alexandru Georgescu <alexandru.c.georgescu>
Component: eclipse-pluginAssignee: Ioana Grigoropol <ioanax.grigoropol>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: ioanax.grigoropol, yp.ep.watcher, yp.watcher
Version: 1.3.1   
Target Milestone: 1.3.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
yocto-bsp none

Description Alexandru Georgescu 2013-03-01 10:14:10 UTC 
Created attachment 1099 [details]
yocto-bsp

ENVIRONMENT USED
HOST: ubuntu 12.10 64bit.
Eclipse plugin: http://autobuilder.yoctoproject.org/pub/nightly/20130226-2/eclipse-plugin/juno/


Same behavior as bug https://bugzilla.yoctoproject.org/show_bug.cgi?id=3747, but this time on Danny.


STEPS TO REPRODUCE
1. Perform all the steps to install eclipse plugin.
2. get a poky clone, and check out the commit 98292d1ef1cb44cf96f0a28fbca6439eda55ce1b
3. Open yocto-bsp tool from Eclipse
4. Set the Metadata location to the poky folder.
5. Set up the build location, bsp name, bsp output location
6. Set kernel architecture (e.g. Set to qemu, and qemu architecture to i386 (or any combination))
7. Press next and in the yocto-bsp properties page select the kernel (e.g. linux-yocto_3.4)

EXPECTED RESULTS
7. Any kernel version can be selected

ACTUAL RESULT
7. An error appears (see attachment)

OTHER COMMENTS
Listing qemu in command line  works:
Comment 1 Jessica 2013-03-01 19:43:30 UTC 
http://git.yoctoproject.org/cgit.cgi/eclipse-poky/commit/?h=danny&id=c507f79de9682fb1b304b3c64aef6a1da5253d2f

Transfer the bug to Ioana since if it still fails, probably she's the better person to debug locally.
Comment 2 Ioana Grigoropol 2013-03-06 12:00:56 UTC 
"sh" is still used on danny branch when creating build directory, and thus the error still appears.
I have sent a oneliner patch to the mailing list in order to fix this. My guess is that this issue is present on master too, but the errors is not reproductible.
Comment 4 Alexandru Georgescu 2013-11-18 14:08:48 UTC 
verified