From: Luiz Capitulino <lcapitulino@redhat.com>
To: jforbes@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [STABLE 1/4] configure: Copy test data to build directory
Date: Fri, 16 Sep 2011 13:30:16 -0300 [thread overview]
Message-ID: <1316190619-4611-2-git-send-email-lcapitulino@redhat.com> (raw)
In-Reply-To: <1316190619-4611-1-git-send-email-lcapitulino@redhat.com>
The QDict unit-tests (check-qdict) will fail when ran on a different
build directory. That's, it only works when ran on the source dir.
This happens because its data file (qdict-test-data.txt) is not
copied to the build dir. Fix it.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
(cherry picked from commit 70371cfbf1b5bac6471928f5e30356cb6f7d1187)
Conflicts:
configure
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
---
configure | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure b/configure
index 3d39d1b..c55be36 100755
--- a/configure
+++ b/configure
@@ -3566,7 +3566,7 @@ DIRS="$DIRS roms/seabios roms/vgabios"
DIRS="$DIRS fsdev ui"
DIRS="$DIRS qapi"
DIRS="$DIRS qga"
-FILES="Makefile tests/Makefile"
+FILES="Makefile tests/Makefile qdict-test-data.txt"
FILES="$FILES tests/cris/Makefile tests/cris/.gdbinit"
FILES="$FILES pc-bios/optionrom/Makefile pc-bios/keymaps"
FILES="$FILES pc-bios/spapr-rtas/Makefile"
--
1.7.7.rc0.72.g4b5ea
next prev parent reply other threads:[~2011-09-16 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 16:30 [Qemu-devel] [STABLE 0/4]: QMP/Monitor stable branch fixes Luiz Capitulino
2011-09-16 16:30 ` Luiz Capitulino [this message]
2011-09-16 16:30 ` [Qemu-devel] [STABLE 2/4] Fix qjson test of solidus encoding Luiz Capitulino
2011-09-16 16:30 ` [Qemu-devel] [STABLE 3/4] monitor: fix build breakage with --disable-vnc Luiz Capitulino
2011-09-16 17:40 ` Justin M. Forbes
2011-09-16 18:00 ` Luiz Capitulino
2011-09-16 16:30 ` [Qemu-devel] [STABLE 4/4] monitor: fix build breakage for !CONFIG_VNC Luiz Capitulino
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=1316190619-4611-2-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=jforbes@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).