From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, f4bug@amsat.org
Subject: Re: [Qemu-devel] [PATCH 2/2] docker: fedora: include more build dependencies
Date: Fri, 16 Mar 2018 13:46:31 +0100 [thread overview]
Message-ID: <a3dc55f7-df1e-ba87-761f-cf783d167c15@redhat.com> (raw)
In-Reply-To: <20180316124505.GH3066@redhat.com>
On 16/03/2018 13:45, Daniel P. Berrangé wrote:
> On Fri, Mar 16, 2018 at 01:25:40PM +0100, Paolo Bonzini wrote:
>> Install optional dependencies of QEMU to get better coverage.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>> tests/docker/dockerfiles/fedora.docker | 67 ++++++++++++++++++++++++++++------
>> 1 file changed, 55 insertions(+), 12 deletions(-)
>>
>> diff --git a/tests/docker/dockerfiles/fedora.docker b/tests/docker/dockerfiles/fedora.docker
>> index be3566325c..6d810f6a92 100644
>> --- a/tests/docker/dockerfiles/fedora.docker
>> +++ b/tests/docker/dockerfiles/fedora.docker
>> @@ -1,18 +1,61 @@
>> FROM fedora:27
>> ENV PACKAGES \
>> ccache gettext git tar PyYAML sparse flex bison python3 bzip2 hostname \
>> - glib2-devel pixman-devel zlib-devel SDL-devel libfdt-devel \
>> - gcc gcc-c++ llvm clang make perl which bc findutils libaio-devel \
>> - nettle-devel libasan libubsan \
>> - mingw32-pixman mingw32-glib2 mingw32-gmp mingw32-SDL2 mingw32-pkg-config \
>> - mingw32-gtk3 mingw32-gnutls mingw32-nettle mingw32-libtasn1 \
>> - mingw32-libjpeg-turbo mingw32-libpng mingw32-curl mingw32-libssh2 \
>> - mingw32-bzip2 \
>> - mingw64-pixman mingw64-glib2 mingw64-gmp mingw64-SDL2 mingw64-pkg-config \
>> - mingw64-gtk3 mingw64-gnutls mingw64-nettle mingw64-libtasn1 \
>> - mingw64-libjpeg-turbo mingw64-libpng mingw64-curl mingw64-libssh2 \
>> - mingw64-bzip2
>> -ENV QEMU_CONFIGURE_OPTS --python=/usr/bin/python3
>> + gcc gcc-c++ llvm clang make perl which bc findutils libasan libubsan \
>> + alsa-lib-devel \
>> + bluez-libs-devel \
>> + brlapi-devel \
>> + bzip2-devel mingw32-bzip2 mingw64-bzip2 \
>> + cyrus-sasl-devel \
>> + device-mapper-multipath-devel \
>> + glib2-devel mingw32-glib2 mingw64-glib2 \
>
> No need for glib as that's pulled in automatically by gtk
We use it, so (unlike nettle-devel and nss-devel) I think it should be
added anyway.
>> + nettle-devel mingw32-nettle mingw64-nettle \
>
> nettle should be pulled in automatically by gnutls
> if it were needed - we automatically link against
> whatever gnutls pulls in.
>
>> + nss-devel \
>
> nss-devel is not required by anything.
Yeah, libcacard uses it but we install its own devel package.
Paolo
prev parent reply other threads:[~2018-03-16 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 12:25 [Qemu-devel] [PATCH 0/2] docker: update package list for fedora image Paolo Bonzini
2018-03-16 12:25 ` [Qemu-devel] [PATCH 1/2] docker: test-mingw: use SDL2 and GTK+3 Paolo Bonzini
2018-03-16 12:41 ` Daniel P. Berrangé
2018-03-16 12:55 ` Philippe Mathieu-Daudé
2018-03-16 12:25 ` [Qemu-devel] [PATCH 2/2] docker: fedora: include more build dependencies Paolo Bonzini
2018-03-16 12:45 ` Daniel P. Berrangé
2018-03-16 12:46 ` Paolo Bonzini [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=a3dc55f7-df1e-ba87-761f-cf783d167c15@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=famz@redhat.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 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).