[maemo-developers] qemu 0.10
From: Juha Kallioinen juha.kallioinen at nokia.comDate: Mon Mar 9 14:28:12 EET 2009
- Previous message: qemu 0.10
- Next message: qemu 0.10
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ext Cornelius Hald wrote: > Thanks for the input Eero! I already tried to compiled qemu using the X86 > and the HOST target, but the build always failed. Now I compiled a static > binary on my host and using that it works somehow. > > [sbox-DIABLO_ARMEL: ~] > qemu-arm-0.10 hello Hello world > > But the problem is now, that if I call the ARM binary directly it looks > like it's not really passed as an argument to qemu. Instead qemu is > called without arguments, or with wrong arguments. Maybe the arguments > are not 100% compatible between 0.9 and 0.10. > ... > Does anyone know where it's defined how the qemu binary is called? Hi, unfortunately you can't use the upstream qemu sources directly to build a functional qemu for Scratchbox1. There are a few patches that need to be applied and you'll need to link it with libsb too. If you'd like, take a look at the patches and sources of the latest cputransp devkit that's available in scratchbox.org: http://scratchbox.org/download/files/sbox-releases/apophis/src/scratchbox-devkit-cputransp-qemu-arm-cvs-m-1.0.9/ You'll also need to copy the support for the -sbox-call command line parameter from the source tarball (for some reason there's not a patch for that). This will take care of the argument passing for you. Qemu for Scratchbox1 has been statically built in a debian etch chroot environment because the host-compiler side of Scratchbox1 is too ancient to build it. There will be a cputransp devkit release with the 0.10 based qemu at some point. Cheers, Juha -- Juha Kallioinen
- Previous message: qemu 0.10
- Next message: qemu 0.10
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]