qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: [PATCH-for-5.0 v2 2/4] tests/docker: Install gcrypt devel package in Debian image
Date: Sun, 22 Mar 2020 13:01:02 +0100	[thread overview]
Message-ID: <20200322120104.21267-3-philmd@redhat.com> (raw)
In-Reply-To: <20200322120104.21267-1-philmd@redhat.com>

In commit 6f8bbb374be we enabled building with the gcrypt library
on the the Debian 'x86 host', which was based on Debian Stretch.
Later in commit 698a71edbed we upgraded the Debian base image to
Buster.

Apparently Debian Stretch was listing gcrypt as a QEMU dependency,
but this is not the case anymore in Buster, so we need to install
it manually (it it not listed by 'apt-get -s build-dep qemu' in
the common debian10.docker anymore). This fixes:

 $ ../configure $QEMU_CONFIGURE_OPTS

  ERROR: User requested feature gcrypt
         configure was not able to find it.
         Install gcrypt devel >= 1.5.0

Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
---
v2: Reword description, do not use 'Fixes:' tag (Aleksandar)
---
 tests/docker/dockerfiles/debian-amd64.docker | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/docker/dockerfiles/debian-amd64.docker b/tests/docker/dockerfiles/debian-amd64.docker
index d4849f509f..957f0bc2e7 100644
--- a/tests/docker/dockerfiles/debian-amd64.docker
+++ b/tests/docker/dockerfiles/debian-amd64.docker
@@ -16,6 +16,7 @@ RUN apt update && \
     apt install -y --no-install-recommends \
         libbz2-dev \
         liblzo2-dev \
+        libgcrypt20-dev \
         librdmacm-dev \
         libsasl2-dev \
         libsnappy-dev \
-- 
2.21.1



  parent reply	other threads:[~2020-03-22 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 12:01 [PATCH-for-5.0 v2 0/4] tests/docker: Fixes for 5.0 Philippe Mathieu-Daudé
2020-03-22 12:01 ` [PATCH-for-5.0 v2 1/4] tests/docker: Keep package list sorted Philippe Mathieu-Daudé
2020-03-22 12:01 ` Philippe Mathieu-Daudé [this message]
2020-03-23 10:08   ` [PATCH-for-5.0 v2 2/4] tests/docker: Install gcrypt devel package in Debian image Philippe Mathieu-Daudé
2020-03-22 12:01 ` [PATCH-for-5.0 v2 3/4] tests/docker: Use Python3 PyYAML in the Fedora image Philippe Mathieu-Daudé
2020-03-22 12:01 ` [PATCH-for-5.0 v2 4/4] tests/docker: Add libepoxy and libudev packages to " Philippe Mathieu-Daudé
2020-03-23  9:58 ` [PATCH-for-5.0 v2 0/4] tests/docker: Fixes for 5.0 Alex Bennée
2020-03-23 10:06   ` Philippe Mathieu-Daudé

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=20200322120104.21267-3-philmd@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=fam@euphon.net \
    --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 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).