On 11/14/2012 10:50 AM, Darren Hart wrote: > runqemu doesn't quite know what to make of poky-tiny :-) Try the following: > > $ qemu-system-i386 -kernel path/to/kernel -initrd path/to/image.cpio.gz > -nographic -append "console=ttyS0 root=/dev/ram0"
Ahh. That's helpful. Thanks. > I really need to get the poky-tiny docs going... right after I finish > these kernel docs I guess... anyone want to volunteer? I'd be happy to write some stuff up. It wouldn't be exhaustive, but I could document what I've found out about (the LIBC_FEATURE stuff, and some of the dependencies I've found, as well as invocation tips and some of the differences between the poky default and poky-tiny packages and features). Where would you like it? Is there a wiki page or a doc already started? >>> >>>> >>>> Has anyone seen this type of error before, or can provide some >>>> hints of what to check or adjust to fix this? >>> >>> Yup, it's wide characters being required by diffutils and being excluded >>> by the poky-tiny DISTRO_FEATURES_LIBC assignment. If supported by >>> diffutils, we might be able to test ENABLE_WIDEC in diffutils and >>> configure accordingly (see the ncurses recipes for an example). >> >> I'll poke around. I'm curious why poky-tiny core-image-minimal built >> OK, but core-image-minimal-initramfs didn't. I didn't expect >> any difference in target-side binaries between the two - only some >> changes in the image build steps. >> >> Thanks for the tips. I'll check it out. > > Let me know what you find out. I thought the initramfs had the installer > in it, but maybe that's included by some other mechanism. Will do. -- Tim ============================= Tim Bird Architecture Group Chair, CE Workgroup of the Linux Foundation Senior Staff Engineer, Sony Network Entertainment ============================= _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
