From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: build broken with --enable-gcrypt
Date: Fri, 28 Aug 2020 10:02:07 +0100 [thread overview]
Message-ID: <20200828090207.GF224144@redhat.com> (raw)
In-Reply-To: <046eb29c-9c68-1baf-846e-decd65f567e0@linaro.org>
On Thu, Aug 27, 2020 at 02:18:46PM -0700, Richard Henderson wrote:
> The meson conversion seems to have not been properly accomplished for the
> gcrypt option: we fail to link against -lgcrypt.
>
> I tried aping the nettle bits, like the following, but it has no effect. I
> don't understand how the "nettle" token works, honestly, since it doesn't
> appear to be used at all.
Hmm, a red flag that we're missing CI coverage of the different
crypto backends. I'll look into fixing this and the meson issue.
> diff --git a/configure b/configure
> index b1e11397a8..4fd50c0275 100755
> --- a/configure
> +++ b/configure
> @@ -6972,6 +6972,8 @@ if test "$gcrypt" = "yes" ; then
> if test "$gcrypt_hmac" = "yes" ; then
> echo "CONFIG_GCRYPT_HMAC=y" >> $config_host_mak
> fi
> + echo "GCRYPT_CFLAGS=$gcrypt_cflags" >> $config_host_mak
> + echo "GCRYPT_LIBS=$gcrypt_libs" >> $config_host_mak
> fi
> if test "$nettle" = "yes" ; then
> echo "CONFIG_NETTLE=y" >> $config_host_mak
> diff --git a/meson.build b/meson.build
> index f0fe5f8799..d45c548191 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -108,6 +108,11 @@ if 'CONFIG_NETTLE' in config_host
> nettle = declare_dependency(compile_args: config_host['NETTLE_CFLAGS'].split(),
> link_args: config_host['NETTLE_LIBS'].split())
> endif
> +gcrypt = not_found
> +if 'CONFIG_GCRYPT' in config_host
> + gcrypt = declare_dependency(compile_args: config_host['GCRYPT_CFLAGS'].split(),
> + link_args: config_host['GCRYPT_LIBS'].split())
> +endif
> gnutls = not_found
> if 'CONFIG_GNUTLS' in config_host
> gnutls = declare_dependency(compile_args: config_host['GNUTLS_CFLAGS'].split(),
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 :|
prev parent reply other threads:[~2020-08-28 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 21:18 build broken with --enable-gcrypt Richard Henderson
2020-08-28 9:02 ` 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=20200828090207.GF224144@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).