From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: kamil@netbsd.org, brad@comstyle.com,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [RFC PATCH 0/3] vmbuild tweaks for BSD targets
Date: Mon, 21 Jan 2019 17:15:40 +0000 [thread overview]
Message-ID: <20190121171543.32422-1-alex.bennee@linaro.org> (raw)
Hi,
While I was digging through the BSD failures on my failed fpu/next PR
I realised the build wasn't quite as flexible as it could be. These
patches expose BUILD_TARGET, TARGET_LIST and EXTRA_CONFIGURE_OPTS to
the vmbuild machinery so you can "quickly" run a subset of your build
via the VMs.
Currently OpenBSD hasn't been tweaked because make check fails on
that. If any of the OpenBSD folk wish to chime in on why that would be
nice.
Alex Bennée (3):
tests/vm: call make check directly for netbsd/freebsd
tests/vm: add --build-target option
tests/vm: expose BUILD_TARGET, TARGET_LIST and EXTRA_CONFIGURE_OPTS
tests/vm/Makefile.include | 10 +++++++++-
tests/vm/basevm.py | 3 +++
tests/vm/freebsd | 3 +--
tests/vm/netbsd | 3 +--
4 files changed, 14 insertions(+), 5 deletions(-)
--
2.17.1
next reply other threads:[~2019-01-21 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 17:15 Alex Bennée [this message]
2019-01-21 17:15 ` [Qemu-devel] [RFC PATCH 1/3] tests/vm: call make check directly for netbsd/freebsd Alex Bennée
2019-01-21 22:53 ` Philippe Mathieu-Daudé
2019-01-24 15:35 ` Philippe Mathieu-Daudé
2019-01-21 17:15 ` [Qemu-devel] [RFC PATCH 2/3] tests/vm: add --build-target option Alex Bennée
2019-01-21 22:54 ` Philippe Mathieu-Daudé
2019-01-23 20:13 ` Philippe Mathieu-Daudé
2019-01-21 17:15 ` [Qemu-devel] [RFC PATCH 3/3] tests/vm: expose BUILD_TARGET, TARGET_LIST and EXTRA_CONFIGURE_OPTS Alex Bennée
2019-01-21 22:57 ` 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=20190121171543.32422-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=brad@comstyle.com \
--cc=kamil@netbsd.org \
--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).