On 09/15/15 12:03, Andy Pont wrote: > Mark wrote... > >>> Bit of a newbie question (probably) but what is the easiest way to dump >>> sysvinit and use Busybox init in a core-image-minimal image? >> It has been a while since I've done this. But unless things have changed >> dramatically. You will need to define your own custom image. > On the basis that sounded like more hard work than I have time for I thought > I would try switching to systemd. Following the instructions in the dev > manual [1]. > > If I add the extra variables to build/conf/local.conf then with the machine > type set to genericx86 I get this build error: > > ERROR: Function failed: do_configure (log file is located at > XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure > .1926) > ERROR: Logfile of failure stored in: > XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure > .1926 > Log data follows: > | DEBUG: Executing python function sysroot_cleansstate > | DEBUG: Python function sysroot_cleansstate finished > | DEBUG: Executing shell function autotools_preconfigure > | DEBUG: Shell function autotools_preconfigure finished > | DEBUG: Executing python function autotools_copy_aclocals > | DEBUG: Python function autotools_copy_aclocals finished > | DEBUG: Executing shell function do_configure > | > | ERROR: User requested feature sdl > | configure was not able to find it. > | Install SDL devel > > I'm guessing that this is me being dim and that build/conf/local.conf isn't > what the documentation refers to as "your distribution configuration file". > Can someone point me in the right direction?
I think the qemu build is looking for your build machine's native SDL (or SDL-devel) so that the resulting qemu can run. Usually a conf/local.conf includes the following lines: PACKAGECONFIG_append_pn-qemu-native = " sdl" PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" ASSUME_PROVIDED += "libsdl-native" I think if you remove/comment-out the last of those 3 lines or install your host's SDL-devel package you'll solve this issue (?) -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto