From: Kevin Wolf <kwolf@redhat.com>
To: qemu@buildbot.b1-systems.de
Cc: qemu-devel@nongnu.org, gollub@b1-systems.de, agraf@suse.de,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on block_mingw32
Date: Wed, 24 Oct 2012 11:16:38 +0200 [thread overview]
Message-ID: <5087B1F6.1030206@redhat.com> (raw)
In-Reply-To: <20121024010551.093214172A@buildbot.b1-systems.de>
Am 24.10.2012 03:05, schrieb qemu@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder block_mingw32 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/block_mingw32/builds/363
>
> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>
> Buildslave for this Build: kraxel_rhel61
>
> Build Reason: The Nightly scheduler named 'nightly_block' triggered this build
> Build Source Stamp: [branch block] HEAD
> Blamelist:
>
> BUILD FAILED: failed compile
>
> sincerely,
> -The Buildbot
Luiz, this is yours:
CC i386-softmmu/exec.o
In file included from
/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0/glib/gthread.h:36,
from
/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0/glib/gasyncqueue.h:34,
from
/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0/glib.h:34,
from
/home/buildbot/slave-public/block_mingw32/build/qemu-common.h:41,
from
/home/buildbot/slave-public/block_mingw32/build/exec.c:27:
/usr/i686-pc-mingw32/sys-root/mingw/include/glib-2.0/glib/gutils.h:290:
warning: redundant redeclaration of 'atexit'
/usr/i686-pc-mingw32/sys-root/mingw/include/stdlib.h:371: note: previous
declaration of 'atexit' was here
/home/buildbot/slave-public/block_mingw32/build/exec.c: In function
'qemu_ram_alloc_from_ptr':
/home/buildbot/slave-public/block_mingw32/build/exec.c:2574: error:
'QEMU_MADV_HUGEPAGE' undeclared (first use in this function)
/home/buildbot/slave-public/block_mingw32/build/exec.c:2574: error:
(Each undeclared identifier is reported only once
/home/buildbot/slave-public/block_mingw32/build/exec.c:2574: error: for
each function it appears in.)
make[1]: *** [exec.o] Error 1
make: *** [subdir-i386-softmmu] Error 2
next prev parent reply other threads:[~2012-10-24 9:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 1:05 [Qemu-devel] buildbot failure in qemu on block_mingw32 qemu
2012-10-24 9:16 ` Kevin Wolf [this message]
2012-10-24 11:39 ` Luiz Capitulino
-- strict thread matches above, loose matches on Subject: below --
2013-01-16 0:06 qemu
2013-01-08 0:06 qemu
2013-01-09 8:53 ` Stefan Hajnoczi
2013-01-09 17:16 ` Stefan Weil
2013-01-10 12:44 ` Stefan Hajnoczi
2013-01-10 13:08 ` Gerd Hoffmann
2012-12-17 0:23 qemu
2012-11-20 0:04 qemu
2012-11-20 13:36 ` Stefan Hajnoczi
2012-11-20 13:49 ` Anthony Liguori
2012-10-20 1:04 qemu
2012-10-22 12:30 ` Kevin Wolf
2012-10-22 13:54 ` Corey Bryant
2012-09-20 6:12 qemu
2012-09-15 1:06 qemu
2012-09-08 1:38 qemu
2012-08-15 1:04 qemu
2012-08-09 1:04 qemu
2012-08-07 1:03 qemu
2012-07-11 1:04 qemu
2012-06-08 1:54 qemu
2012-06-08 9:07 ` Stefan Hajnoczi
2012-06-08 9:51 ` Max Filippov
2012-06-05 1:50 qemu
2012-05-10 1:04 qemu
2012-05-10 7:28 ` Paolo Bonzini
2012-04-04 1:43 qemu
2012-03-03 2:05 qemu
2012-03-03 9:06 ` Stefan Weil
2012-02-20 6:44 qemu
2012-01-24 2:05 qemu
2011-12-16 2:06 qemu
2011-11-23 2:04 qemu
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=5087B1F6.1030206@redhat.com \
--to=kwolf@redhat.com \
--cc=agraf@suse.de \
--cc=gollub@b1-systems.de \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu@buildbot.b1-systems.de \
/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).