From: Gerd Hoffmann <kraxel@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Fwd: buildbot failure in qemu on openbsd-default
Date: Fri, 02 Nov 2012 16:25:09 +0100 [thread overview]
Message-ID: <5093E5D5.9010602@redhat.com> (raw)
In-Reply-To: <20121101201201.A7F474027F@spunk.home.kraxel.org>
-------- Original Message --------
Subject: buildbot failure in qemu on openbsd-default
Date: Thu, 01 Nov 2012 21:12:01 +0100
From: buildbot@spunk.home.kraxel.org
To: kraxel+bb@gmail.com
The Buildbot has detected a failed build on builder openbsd-default
while building qemu.
Full details are available at:
http://www.kraxel.org/bb/builders/openbsd-default/builds/866
Buildbot URL: http://www.kraxel.org/bb/
Buildslave for this Build: openbsd
Build Reason: scheduler
Build Source Stamp: [branch master] 4ba79505f43bd0ace35c3fe42197eb02e7e0478e
Blamelist: Andreas Färber <afaerber@suse.de>,Anthony Liguori
<aliguori@us.ibm.com>,Dmitry Fleytman <dmitry@daynix.com>,Don Slutz
<Don@CloudSwitch.com>,Eduardo Habkost <ehabkost@redhat.com>,Gabriel L.
Somlo <gsomlo@gmail.com>,Gerd Hoffmann <kraxel@redhat.com>,Igor Mammedov
<imammedo@redhat.com>,Jan Kiszka <jan.kiszka@siemens.com>,Lei Li
<lilei@linux.vnet.ibm.com>,Marcelo Tosatti <mtosatti@redhat.com>,Paolo
Bonzini <pbonzini@redhat.com>,Peter Maydell
<peter.maydell@linaro.org>,Stefan Hajnoczi <stefanha@redhat.com>
BUILD FAILED: failed compile
sincerely,
-The Buildbot
========== log tail ==========
GEN qapi-visit.c
CC qapi-visit.o
CC qapi/qapi-visit-core.o
CC qapi/qapi-dealloc-visitor.o
CC qapi/qmp-input-visitor.o
CC qapi/qmp-output-visitor.o
CC qapi/qmp-registry.o
CC qapi/qmp-dispatch.o
CC qapi/string-input-visitor.o
CC qapi/string-output-visitor.o
CC qint.o
CC qstring.o
CC qdict.o
CC qlist.o
CC qfloat.o
CC qbool.o
CC qjson.o
CC json-lexer.o
CC json-streamer.o
CC json-parser.o
CC qerror.o
CC error.o
CC qemu-error.o
LINK qemu-ga
/usr/local/lib/libglib-2.0.so.2992.0: warning: vsprintf() is often
misused, please use vsnprintf()
/usr/local/lib/libglib-2.0.so.2992.0: warning: stpcpy() is dangerous GNU
crap; don't use it
/usr/local/lib/libglib-2.0.so.2992.0: warning: strcpy() is almost always
misused, please use strlcpy()
/usr/local/lib/libglib-2.0.so.2992.0: warning: sprintf() is often
misused, please use snprintf()
qemu-thread-posix.o(.text+0x3ea): In function `qemu_sem_timedwait':
: undefined reference to `sem_timedwait'
collect2: ld returned 1 exit status
gmake: *** [qemu-ga] Error 1
========== full log ==========
http://www.kraxel.org/bb/builders/openbsd-default/builds/866/steps/compile/logs/stdio
next parent reply other threads:[~2012-11-02 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121101201201.A7F474027F@spunk.home.kraxel.org>
2012-11-02 15:25 ` Gerd Hoffmann [this message]
2012-11-02 16:22 ` [Qemu-devel] Fwd: buildbot failure in qemu on openbsd-default Anthony Liguori
2012-11-02 17:53 ` Paolo Bonzini
[not found] <20121115150614.7EF3A400FC@spunk.home.kraxel.org>
2012-11-15 16:08 ` Gerd Hoffmann
[not found] <20120508173000.A488B40248@spunk.home.kraxel.org>
2012-05-09 8:43 ` Gerd Hoffmann
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=5093E5D5.9010602@redhat.com \
--to=kraxel@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).