From: Yao Zi <ziyao@disroot.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] meson.build: fix libgcrypt detection on system without libgcrypt-config
Date: Mon, 15 Jul 2024 21:21:25 +0800 [thread overview]
Message-ID: <ZpUiVe4wTHm7lmpP@ziyaolaptop.my.domain> (raw)
In-Reply-To: <ZpE1ApH6sWuRdf-L@redhat.com>
On Fri, Jul 12, 2024 at 02:52:02PM +0100, Daniel P. Berrangé wrote:
> On Sat, Jul 06, 2024 at 08:12:26PM +0000, Yao Zi wrote:
> > libgcrypt starts providing correct pkg-config configuration and dropping
> > libgcrypt-config since 1.11.0. So use auto method for detection of
> > libgcrypt, in which meson will try both pkg-config and libgcrypt-config.
>
> The pkg-config file seems to be provided since 1.9 in fact.
>
> Where do you see that ligcrypt-config is dropped ?
Commit 2db5b5e9
("build: When no gpg-error-config, not install libgcrypt-config")[1] in
libgcrypt says that
> When system will migrate use of gpgrt-config and removal of
> gpg-error-config, libgcrypt-config will not be installed
1.11.0 is the first release containing this commit.
> It still
> exists in the gcrypt git repo and in Fedora 1.11.0 packages.
It does not on Arch Linux. For Fedora, I have no idea.
[1]: https://github.com/gpg/libgcrypt/commit/2db5b5e995c21c5bd9cd193c2ed1109ba9b1a440
[2]: https://archlinux.org/packages/core/x86_64/libgcrypt/
Best regards,
Yao Zi
prev parent reply other threads:[~2024-07-15 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 20:12 [PATCH] meson.build: fix libgcrypt detection on system without libgcrypt-config Yao Zi
2024-07-12 13:52 ` Daniel P. Berrangé
2024-07-15 13:21 ` Yao Zi [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=ZpUiVe4wTHm7lmpP@ziyaolaptop.my.domain \
--to=ziyao@disroot.org \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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 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).