All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Michael Tokarev <mjt@tls.msk.ru>
Subject: libslirp and static linking
Date: Fri, 5 Aug 2022 17:13:28 +0100	[thread overview]
Message-ID: <CAFEAcA87=Xs8vd8e+eHzSFboWOUcAhJUuFvuG1gzw+Zs_M-DyQ@mail.gmail.com> (raw)

Hi; I noticed today that Debian's libslirp-dev package doesn't ship
a static library version of libslirp. I was going to file a Debian
bug about that, but then looking at upstream 'libslirp' I found
that its README.md
https://gitlab.freedesktop.org/slirp/libslirp
only documents how to build a shared library libslirp, and says
"(QEMU may build with the submodule static library using --enable-slirp=git)"

So:
(1) is it possible to build the separate libslirp package as
    a static library currently?
(2) if not, can it be enhanced to do so?
(3) otherwise, is upstream QEMU going to have to retain the
    git submodule just for the static linking case ?


I also found that at least the pkg-config file shipped with
Ubuntu libslirp-dev 4.1.0-2ubuntu2.2 results in 'configure --static'
incorrectly detecting that libslirp is present, even though that
package does not ship a static library. I'm not sure whether that's
a bug in the pkg-config file, in the Debian/Ubuntu packaging, or in
QEMU's library probing code...

thanks
-- PMM


             reply	other threads:[~2022-08-05 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05 16:13 Peter Maydell [this message]
2022-08-05 17:33 ` libslirp and static linking Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFEAcA87=Xs8vd8e+eHzSFboWOUcAhJUuFvuG1gzw+Zs_M-DyQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.