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>,
"Claudio Fontana" <cfontana@suse.de>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH 0/2] tests: Remove unused bison/flex packages
Date: Fri, 15 May 2020 10:31:22 +0200 [thread overview]
Message-ID: <20200515083124.5536-1-philmd@redhat.com> (raw)
I was misguided by libdtc warnings, and thought bison/flex
were required to build QEMU, so installed them in docker
(and they also ended in the VM scripts).
Claudio's series "libfdt: build only the strict necessary"
even silents the warnings.
Based-on: <20200514193811.6798-1-cfontana@suse.de>
Philippe Mathieu-Daudé (2):
tests/docker: Remove flex/bison packages
tests/vm: Remove flex/bison packages
tests/docker/dockerfiles/centos7.docker | 2 --
tests/docker/dockerfiles/centos8.docker | 2 --
tests/docker/dockerfiles/debian-xtensa-cross.docker | 2 --
tests/docker/dockerfiles/debian10.docker | 2 --
tests/docker/dockerfiles/debian9.docker | 2 --
tests/docker/dockerfiles/fedora.docker | 2 --
tests/docker/dockerfiles/ubuntu.docker | 2 +-
tests/docker/dockerfiles/ubuntu1804.docker | 2 +-
tests/vm/fedora | 1 -
tests/vm/freebsd | 1 -
tests/vm/netbsd | 1 -
tests/vm/ubuntu.i386 | 2 +-
12 files changed, 3 insertions(+), 18 deletions(-)
--
2.21.3
next reply other threads:[~2020-05-15 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 8:31 Philippe Mathieu-Daudé [this message]
2020-05-15 8:31 ` [PATCH 1/2] tests/docker: Remove flex/bison packages Philippe Mathieu-Daudé
2020-05-15 9:02 ` Claudio Fontana
2020-05-15 9:21 ` Philippe Mathieu-Daudé
2020-05-15 8:31 ` [PATCH 2/2] tests/vm: " Philippe Mathieu-Daudé
2020-05-15 9:23 ` Philippe Mathieu-Daudé
2020-05-15 9:41 ` Claudio Fontana
2020-05-15 9:55 ` 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=20200515083124.5536-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=david@gibson.dropbear.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.