Bug 7629 - devtool build-image wihtin extensible SDK fails when IMAGE_FSTYPES includes "live"
Summary: devtool build-image wihtin extensible SDK fails when IMAGE_FSTYPES includes "...
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.8
Hardware: All Multiple
: Medium+ major
Target Milestone: 2.0
Assignee: Randy Witt
QA Contact: Alexandru Georgescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-04-20 10:28 UTC by Paul Eggleton
Modified: 2015-11-02 16:31 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
Output from strace of mcopy (6.83 KB, text/plain)
2015-04-20 10:28 UTC, Paul Eggleton
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-04-20 10:28:24 UTC
Created attachment 2482 [details]
Output from strace of mcopy

If IMAGE_FSTYPES includes "live" (as it does with the intel-corei7-64 machine in meta-intel), you get the following error when installing:

--------- snip ----------
| mkdosfs 2.11 (12 Mar 2005)
| Error converting to codepage 850 Invalid argument
| Cannot initialize '::'
| Bad target ::/
| WARNING: exit code 1 from a shell command.
| DEBUG: Python function do_bootimg finished
| ERROR: Function failed: build_hddimg (log file is located at /home/paul/extsdk2/tmp/work/intel_corei7_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_bootimg.12435)
--------- snip ----------

This error is from the mcopy command; wrapping the command in strace gives a better idea of what's going wrong:

--------- snip ----------
open("/opt/poky/1.8+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/gconv/gconv-modules.cache", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/opt/poky/1.8+snapshot/sysroots/x86_64-pokysdk-linux/usr/lib/gconv/gconv-modules", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
write(2, "Error converting to codepage 850"..., 50) = 50
close(3)                                = 0
write(2, "Cannot initialize '::'\n", 23) = 23
write(2, "Bad target ::/\n", 15)        = 15
exit_group(1)                           = ?
+++ exited with 1 +++
--------- snip ----------

It appears to be looking in the wrong place for the gconv-modules cache. I'm not yet sure if that's because we are missing something in the sysroot or we failed to do some required relocation.
Comment 1 Paul Eggleton 2015-05-13 16:25:21 UTC
After some discussion with Randy we're thinking that we should fix bug 7590 and then we can drop this bug's priority, since without running do_rootfs during the install it won't show up anymore.
Comment 2 Randy Witt 2015-08-20 17:06:51 UTC
This is because the extensible sdk uses the libc from uninative, and that libc doesn't have the 850 codepage in it.

Most likely this can be fixed by adding the 850 codepage to the libc used by uninative.
Comment 3 Paul Eggleton 2015-10-19 15:35:48 UTC
FWIW I tried adding nativesdk-glibc-gconv-ibm850 to TOOLCHAIN_HOST_TASK in uninative-tarball.bb, but that didn't fix it.
Comment 4 Paul Eggleton 2015-10-19 15:55:57 UTC
Output of an strace that I did now is pretty much the same, it's looking for gconv-modules under the non-relocated default SDK path and of course failing to find them there.
Comment 5 Paul Eggleton 2015-10-20 13:49:20 UTC
So, the failure on install is fixed (see bug 7590) - but the issue still occurs when you run "devtool build-image", so I've retitled the bug.
Comment 6 Paul Eggleton 2015-10-27 10:11:05 UTC
This was fixed by the following commit now in master, although the commit message is somewhat sparse and does not include reference to this bug:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d8d4ce720e5c5823d00c2000d182e0f409240138
Comment 8 Alexandru Georgescu 2015-11-02 16:31:11 UTC
Verified with jethro:370a2916c4559c17952392b872322e8e490b124c


Steps:
1. bitbake core-image-sato -c populate_sdk_ext (for intel-corei7-64 BSP)
2. Install the sdk_ext
3. In a new shell, source the environment and build a core-image-sato-sdk using devtool:
$ devtool build-image core-image-sato-sdk