From: Stefan Weil <sw@weilnetz.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1.1] tests: Fix linker failure for fdc-test
Date: Tue, 15 May 2012 07:33:52 +0200 [thread overview]
Message-ID: <4FB1EAC0.4040604@weilnetz.de> (raw)
In-Reply-To: <1337059639-4936-1-git-send-email-sw@weilnetz.de>
Am 15.05.2012 07:27, schrieb Stefan Weil:
> When QEMU was built with the simple trace backend, linking failed:
> LINK tests/fdc-test oslib-posix.o: In function `trace_qemu_memalign':
> qemu/bin/debug/x86/./trace.h:31: undefined reference to `trace3'
> oslib-posix.o: In function `trace_qemu_vmalloc':
> qemu/bin/debug/x86/./trace.h:35: undefined reference to `trace2'
> oslib-posix.o: In function `trace_qemu_vfree':
> qemu/bin/debug/x86/./trace.h:39: undefined reference to `trace1'
> collect2: error: ld returned 1 exit status make: *** [tests/fdc-test]
> Fehler 1 Signed-off-by: Stefan Weil <sw@weilnetz.de> ---
> tests/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/tests/Makefile b/tests/Makefile index 20e4da9..f1b317a
> 100644 --- a/tests/Makefile +++ b/tests/Makefile @@ -68,7 +68,7 @@
> tests/test-qmp-commands$(EXESUF): tests/test-qmp-commands.o
> tests/test-qmp-marsh tests/rtc-test$(EXESUF): tests/rtc-test.o
> $(trace-obj-y) tests/m48t59-test$(EXESUF): tests/m48t59-test.o
> $(trace-obj-y) -tests/fdc-test$(EXESUF): tests/fdc-test.o
> tests/libqtest.o +tests/fdc-test$(EXESUF): tests/fdc-test.o
> tests/libqtest.o $(trace-obj-y) # QTest rules
... and after this linker failure was fixed, the test reports an error:
GTESTER check-qtest-sparc64
**
ERROR:/home/stefan/src/qemu/qemu.org/qemu/tests/fdc-test.c:120:test_media_change:
assertion failed ((dir) & (DSKCHG) == 0): (0x00000080 == 0x00000000)
GTester: last random seed: R02Sd438078cdc65f1843886ab2983bf20ba
**
ERROR:/home/stefan/src/qemu/qemu.org/qemu/tests/fdc-test.c:120:test_media_change:
assertion failed ((dir) & (DSKCHG) == 0): (0x00000080 == 0x00000000)
GTester: last random seed: R02Sb6ef6a57dc94cacf2d7ba4e3bd34b7a4
I like buildbots. They also fail in the same test with a timeout,
that's why I had run this check.
Regards,
Stefan W.
next prev parent reply other threads:[~2012-05-15 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 5:27 [Qemu-devel] [PATCH 1.1] tests: Fix linker failure for fdc-test Stefan Weil
2012-05-15 5:33 ` Stefan Weil [this message]
2012-05-15 5:48 ` Stefan Weil
2012-05-15 8:01 ` Kevin Wolf
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=4FB1EAC0.4040604@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.com \
--cc=kwolf@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).