Comment 11 for bug 2029431

Is it particularly difficult or time consuming to provide it or what's the
push back? From what I could tell it's not hard to get the build system too
produce both static + dynamic when you build it yourself.

I'll be honest I gave up on my static qemu system (too many other
dependencies that required dynamic for my build) but I do see others
patching & building it or turning off just the right features.

I think "small binary + I want this feature" is a legitimate use case.

On Fri, Aug 18, 2023, 18:36 Michael Cook <email address hidden> wrote:

> I am not sure what I can omit or include. When I omitted it, RaspPi
> image booted up and died when it couldn't find any "net" interfaces. Do
> you have any pointers to using a tap networking interface with qemu and
> docker? I am willing to give it a go, but learning as I go here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2029431
>
> Title:
> Provide static library in libslirp-dev
>
> Status in libslirp package in Ubuntu:
> Fix Released
> Status in libslirp package in Debian:
> Unknown
>
> Bug description:
> QEMU static builds currently fail (among other reasons) because a
> static libslirp is missing from libslirp-dev, as is usual for other
> *-dev packages.
>
> The instructions in https://gitlab.freedesktop.org/slirp/libslirp --
> which say to "(QEMU may build with the submodule static library using
> --enable-slirp=git)" -- do not work anymore as of the patches in
> https://patchwork.kernel.org/project/qemu-
> <email address hidden>/ which removed
> those options completely.
>
> It'd be best if a static library was just provided in every libslirp-
> dev package.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/libslirp/+bug/2029431/+subscriptions
>
>