| Summary: | Package gtk+-2.0 missing from the userbuilt toolchain | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] ADT | Reporter: | Alexandru Georgescu <alexandru.c.georgescu> |
| Component: | adt | Assignee: | Laurentiu Palcu <laurentiu.palcu> |
| Status: | VERIFIED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, liang.li2, poky.adt.watcher, poky.watcher, sgw |
| Version: | 1.4 | ||
| Target Milestone: | 1.4 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Alexandru Georgescu
2013-01-18 14:36:50 UTC
the error also happened on opensuse 12.2 x86_64 and fedora 17 i686 hosts. Hi, THe issue happens actually when using sudoku project, not iptables. Sudoku source code can be downloaded from here: http://sourceforge.net/projects/sudoku-savant/files/sudoku-savant/sudoku-savant-1.3/ When using meta-ide-toolchain bitbake target, only a minimal target sysroot is constructed. Not all libraries are included in it. So, in order for one to compile a certain application, the target SDK image has to be compiled first (for example core-image-sato-sdk) and then extract the target rootfs using runqemu-extract-sdk. Afterwards, the environment setup script has to be manually edited so that the sysroot points to the target rootfs location. Documentation about this procedure can be found here [1], paragraph 2.1.3. Jessica, Do you have anything to add to this? In my opinion this is not a bug, just an usage issue. I did the procedure explained above and the sudoku project compiled just fine. [1] http://www.yoctoproject.org/docs/1.3/adt-manual/adt-manual.html Jessica, Laurentiu, I have looked over the documentation but I can say that it isn't explicitly saying that you have to build an actual core-image-sato-sdk in order to be able to compile a project. quote from the documentation that Laurentiu specified: "Be aware that when you use this method to install the toolchain you still need to separately extract and install the sysroot filesystem. For information on how to do this, see the "Extracting the Root Filesystem" section." As for me, I can interpret that I can use a sysroot downloaded from the autobuilder, which I actually did. It doesn't So how do you should we proceed? Hi Alex, I agree with Laurentiu, it states that you have to extract a target rootfs as sysroot which means you(application developer) need to be responsible that the sysroot contains all the nedded dev packages for your application to compile. So I'm closing this bug as not a bug. I'd say you need to update your test case to either explicitly extract core-image-sato-sdk as your sysroot and modify the environment setup file coordinally. Or bitbake core-image-sato-sdk yourself and use the default sysroot under ../build/tmp/sysroots/qemux86 Thanks, Jessica verified |