All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Brad Smith <brad@comstyle.com>
Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel P . Berrange" <berrange@redhat.com>,
	qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [RFC PATCH for-7.1] Remove the slirp submodule (and only compile with an external libslirp)
Date: Sun, 10 Apr 2022 10:06:31 +0100	[thread overview]
Message-ID: <CAFEAcA-NdeN8S0JXqfrpTiDoUmfZHBXUtdAuRAdDRooTpnYipA@mail.gmail.com> (raw)
In-Reply-To: <72fe734a-8bf6-adc6-474a-47f2006c2f6d@comstyle.com>

On Sun, 10 Apr 2022 at 05:51, Brad Smith <brad@comstyle.com> wrote:
>
> On 4/8/2022 12:47 PM, Thomas Huth wrote:
> > QEMU 7.1 won't support Ubuntu 18.04 anymore, so the last big important
> > distro that did not have a pre-packaged libslirp has been dismissed.
> > All other major distros seem to have a libslirp package in their
> > distribution already - according to repology.org:
> >
> >            Fedora 34: 4.4.0
> >    CentOS 8 (RHEL-8): 4.4.0
> >        Debian Buster: 4.3.1 (in buster-backports)
> >   OpenSUSE Leap 15.3: 4.3.1
> >     Ubuntu LTS 20.04: 4.1.0
> >        FreeBSD Ports: 4.6.1
> >        NetBSD pkgsrc: 4.3.1
> >             Homebrew: 4.6.1
> >          MSYS2 mingw: 4.6.1
> >
> > The only one that still seems to be missing a libslirp package is
> > OpenBSD - but I assume that they can add it to their ports system
> > quickly if required.

> I wish I had seen this earlier as our 7.1 release was just tagged.
>
> I have whipped up a port of 4.6.1 for OpenBSD as it was pretty simple. I
> will
> see about submitting it in a number of days when the tree opens.

How awkward would it be for an end-user who's on OpenBSD 7.1 to
build a QEMU that doesn't have libslirp? (That is, is it easy
and common for an end user to pull in a port of libslirp that only
came along in a later OpenBSD, or would they instead have to
manually compile libslirp themselves from the upstream sources?)

(I'm asking here because if it's painful, then we should perhaps
defer dropping our submodule copy of libslirp a little longer.)

thanks
-- PMM


  reply	other threads:[~2022-04-10  9:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 16:47 [RFC PATCH for-7.1] Remove the slirp submodule (and only compile with an external libslirp) Thomas Huth
2022-04-10  4:49 ` Brad Smith
2022-04-10  9:06   ` Peter Maydell [this message]
2022-04-10 23:50     ` Brad Smith
2022-04-11  6:55       ` Thomas Huth
2022-04-14  7:23         ` Brad Smith
2022-04-19 16:24         ` Daniel P. Berrangé
2022-04-20 10:13           ` Thomas Huth
2022-04-23 22:06             ` Brad Smith
2022-04-11  7:11 ` Paolo Bonzini
2022-04-11  8:11   ` 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=CAFEAcA-NdeN8S0JXqfrpTiDoUmfZHBXUtdAuRAdDRooTpnYipA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=berrange@redhat.com \
    --cc=brad@comstyle.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=thuth@redhat.com \
    /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.