From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] crypto: require gnutls >= 3.1.18 for building QEMU
Date: Mon, 6 Aug 2018 18:08:18 +0100 [thread overview]
Message-ID: <20180806170818.GG20807@redhat.com> (raw)
In-Reply-To: <21544428-4494-da5c-41c6-e72056db2bca@redhat.com>
On Mon, Aug 06, 2018 at 11:58:41AM -0500, Eric Blake wrote:
> On 07/18/2018 07:03 AM, Daniel P. Berrangé wrote:
> > gnutls 3.0.0 was released in 2011 and all the distros that are build
> > target platforms for QEMU [1] include it:
> >
> > RHEL-7: 3.1.18
> > Debian (Stretch): 3.5.8
> > Debian (Jessie): 3.3.8
> > OpenBSD (ports): 3.5.18
> > FreeBSD (ports): 3.5.18
> > OpenSUSE Leap 15: 3.6.2
> > Ubuntu (Xenial): 3.4.10
> > macOS (Homebrew): 3.5.19
> >
> > Based on this, it is reasonable to require gnutls >= 3.1.18 in QEMU
> > which allows for all conditional version checks in the code to be
> > removed.
>
> Looks reasonable.
>
> >
> > [1] https://qemu.weilnetz.de/doc/qemu-doc.html#Supported-build-platforms
> >
>
> Any chance we can get http builds of the docs hosted directly on qemu.org
> someday? But unrelated to your patch.
>
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > @@ -2675,79 +2674,28 @@ fi
> > ##########################################
> > # GNUTLS probe
> > -gnutls_works() {
> > - # Unfortunately some distros have bad pkg-config information for gnutls
> > - # such that it claims to exist but you get a compiler error if you try
> > - # to use the options returned by --libs. Specifically, Ubuntu for --static
> > - # builds doesn't work:
> > - # https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1478035
>
> This bug is still in state NEW, but targets Ubuntu 14.04 and "Package:
> libgnutls-dev 2.12.23-12ubuntu2.2", so is probably indeed old enough that it
> is hopefully a non-issue for gnutls > 3 in the versions of Ubuntu we
> specifically support. However, I'm not enough of an Ubuntu user myself to
> confirm whether things still work, so you'll probably want to collect
> additional R-b or Tested-by before accepting this for qemu 3.1.
FYI, I checked the pkg-config file with gnutls 3 on ubuntu and it did not
appear to have the bug that existed in gnutls 2, so I believe removing
this cruft is safe.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-08-06 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 12:03 [Qemu-devel] [PATCH 0/3] crypto: increase min required gnutls, gcrypt and nettle Daniel P. Berrangé
2018-07-18 12:03 ` [Qemu-devel] [PATCH 1/3] crypto: require gnutls >= 3.1.18 for building QEMU Daniel P. Berrangé
2018-08-06 16:58 ` Eric Blake
2018-08-06 17:08 ` Daniel P. Berrangé [this message]
2018-07-18 12:03 ` [Qemu-devel] [PATCH 2/3] crypto: require libgcrypt >= 1.5.0 " Daniel P. Berrangé
2018-08-06 18:01 ` Eric Blake
2018-07-18 12:03 ` [Qemu-devel] [PATCH 3/3] crypto: require nettle " Daniel P. Berrangé
2018-08-06 18:02 ` Eric Blake
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=20180806170818.GG20807@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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.