On Wed, Jun 29, 2016 at 04:54:42PM +0200, Florian Weimer wrote: > On 06/29/2016 12:34 PM, Daniel P. Berrange wrote: > > On Wed, Jun 29, 2016 at 12:15:02PM +0200, Florian Weimer wrote: > > > On 06/29/2016 12:03 PM, Daniel P. Berrange wrote: > > > > Debian handles this by having several packages [1] > > > > > > > > - qemu-user - the dynamic linked qemu user binaries > > > > - qemu-binfmt - binfmt rules registering the dynamic linked binaries > > > > - qemu-user-static - the static linked qemu user binaries *and* binfmt > > > > rules to register them. The static binaries all > > > > have -static suffix on their name > > > > > > Debian builds static libraries and puts them into their -dev packages. > > > Fedora does not do this systematically. Are all the static libraries you > > > need actually available in Fedora? > > > > Yes, everything we need exists - as mentioned its only glibc-static, > > glib2-static, zlib-static and pcre-static that we need for this. > > In this case, linking statically is indeed an option. > > We currently have little tooling for static libraries. Strictly speaking, > all statically linked libraries have to be rebuilt even for minor glibc > updates because we do not provide ABI compatibility for static linking > (there are no compatibility symbols, static binaries always get the most > recent implementation). Yep, I understand those caveats - the flipside is that most other Linux distros already provide statically linked qemu user emulators with glibc without suffering unduly. So while I accept there are potential problems, it doesn't seem like they're frequent / severe enough to make this approach unviable. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
