On 20 June 2016 at 22:27, Joel Holdsworth <joel.holdswo...@vcatechnology.com> wrote: > The current behaviour was quite unexpected to me - there were no warnings, > and the need to link qemu statically isn't documented anywhere. If you > really believe that static linking is the best answer here, then shouldn't > the shared library option be removed? Because with the shared-library build, > qemu-user is somewhat "broken".
Shared library QEMU works fine for simple use cases ("run a gcc test case", for instance) or where the guest binary is linked statically and doesn't much care where it runs. > But the distros won't like that because of the induced bloat. I don't know of a distro which doesn't ship a statically linked QEMU offhand. Debian, Ubuntu and SUSE certainly all do. You basically need it for the chroot case, which is a really common one. [These days if your distro-in-the-chroot is multiarch you could put all the dynamic libraries for the QEMU binary in it too, but in practice being able to just copy a single binary in is much easier.] thanks -- PMM