From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Luc Michel <luc.michel@amd.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
"Francisco Iglesias" <francisco.iglesias@amd.com>,
"Frederic Konrad" <frederic.konrad@amd.com>
Subject: Re: [PATCH] meson.build: re-add explicit gcrypt/nettle request check
Date: Fri, 10 Jul 2026 10:53:28 +0100 [thread overview]
Message-ID: <alDBGFEqLeaBFdcC@redhat.com> (raw)
In-Reply-To: <20260710075113.35631-1-luc.michel@amd.com>
On Fri, Jul 10, 2026 at 09:51:12AM +0200, Luc Michel wrote:
> c4b3d0074 removed the check that nettle or gcrypt were explicitly
> requested as the crypto library to use, breaking the --enable-nettle and
> --enable-gcrypt options. Re-add the check.
>
> Fixes: c4b3d0074 (crypto: bump min gnutls to 3.7.5)
> Signed-off-by: Luc Michel <luc.michel@amd.com>
> ---
> meson.build | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/meson.build b/meson.build
> index 164328ded83..475c5922030 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -1809,10 +1809,15 @@ crypto_sm3 = not_found
>
> if get_option('nettle').enabled() and get_option('gcrypt').enabled()
> error('Only one of gcrypt & nettle can be enabled')
> endif
>
> +# Explicit nettle/gcrypt request, so ignore gnutls for crypto
> +if get_option('nettle').enabled() or get_option('gcrypt').enabled()
> + gnutls = not_found
> +endif
> +
> if not gnutls.found()
This is not sufficient - if --enable-nettle is given this logic
will fully disable all use of gnutls. We need to retain the use
of nettle for TLS APIs, but exclude it for crypto APIs.
IOW, we need to revert more of c4b3d0074 - can you also bring
back the lines that set the 'gnutls_crypto' variable, so we
can disable gnutls for crypto only, not TLS>
> if (not get_option('gcrypt').auto() or have_system) and not get_option('nettle').enabled()
> gcrypt = dependency('libgcrypt', version: '>=1.9.4',
> required: get_option('gcrypt'))
> # Debian has removed -lgpg-error from libgcrypt-config
> --
> 2.53.0
>
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-07-10 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 7:51 [PATCH] meson.build: re-add explicit gcrypt/nettle request check Luc Michel
2026-07-10 8:57 ` Philippe Mathieu-Daudé
2026-07-10 9:53 ` Daniel P. Berrangé [this message]
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=alDBGFEqLeaBFdcC@redhat.com \
--to=berrange@redhat.com \
--cc=francisco.iglesias@amd.com \
--cc=frederic.konrad@amd.com \
--cc=luc.michel@amd.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@mailo.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.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.