From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Thomas Huth" <thuth@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH v2 0/2] crypto: fix build with gcrypt
Date: Tue, 1 Sep 2020 14:30:48 +0100 [thread overview]
Message-ID: <20200901133050.381844-1-berrange@redhat.com> (raw)
The build system failed to add gcrypt flags and also didn't link to
gnutls in all scenarios. This was missed because of the lack of CI
coverage for various build scenarios
Changed in v2:
- Change way we add library dependencies in meson rules
to fix linux-user build with gcrypt/gnutls too.
- Extend CI coverage to test 1 system and 1 linux-user
build with each crypto combination, not merely tools.
Daniel P. Berrangé (2):
crypto: fix build with gcrypt enabled
gitlab: expand test coverage for crypto builds
.gitlab-ci.yml | 69 +++++++++++++++++++++++++
configure | 2 +
crypto/meson.build | 42 +++++++++++----
meson.build | 5 ++
tests/docker/dockerfiles/centos7.docker | 2 +
tests/docker/dockerfiles/centos8.docker | 1 +
6 files changed, 110 insertions(+), 11 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-01 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 13:30 Daniel P. Berrangé [this message]
2020-09-01 13:30 ` [PATCH v2 1/2] crypto: fix build with gcrypt enabled Daniel P. Berrangé
2020-09-01 14:18 ` Alex Bennée
2020-09-01 13:30 ` [PATCH v2 2/2] gitlab: expand test coverage for crypto builds Daniel P. Berrangé
2020-09-01 15:10 ` Philippe Mathieu-Daudé
2020-09-01 15:27 ` Daniel P. Berrangé
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=20200901133050.381844-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).