qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Fwd: buildbot failure in qemu on fedora-mingw32
Date: Thu, 07 Jun 2012 19:54:44 +0800	[thread overview]
Message-ID: <4FD09684.5070604@codemonkey.ws> (raw)
In-Reply-To: <4FD094C2.5040301@gmail.com>

Luiz/Wen Congyang: ^

Regards,

Anthony Liguori

On 06/07/2012 07:47 PM, Gerd Hoffmann wrote:
>
>
> -------- Original Message --------
> Subject: buildbot failure in qemu on fedora-mingw32
> Date: Thu, 07 Jun 2012 13:30:54 +0200
> From: buildbot@spunk.home.kraxel.org
> To: kraxel+bb@gmail.com
>
> The Buildbot has detected a failed build on builder fedora-mingw32 while
> building qemu.
> Full details are available at:
>   http://www.kraxel.org/bb/builders/fedora-mingw32/builds/130
>
> Buildbot URL: http://www.kraxel.org/bb/
>
> Buildslave for this Build: fedora
>
> Build Reason: scheduler
> Build Source Stamp: [branch kraxel-spice]
> 901a8dd46efb5820796000d05f39d3677633bf64
> Blamelist: Alon Levy<alevy@redhat.com>,Anthony Liguori
> <aliguori@us.ibm.com>,Daniel P. Berrange<berrange@redhat.com>,Luiz
> Capitulino<lcapitulino@redhat.com>,Wen Congyang<wency@cn.fujitsu.com>
>
> BUILD FAILED: failed compile
>
> sincerely,
>   -The Buildbot
>
>
> ========== log tail ==========
>    CC    i386-softmmu/virtio-blk.o
>    CC    i386-softmmu/virtio-balloon.o
>    CC    i386-softmmu/virtio-net.o
>    CC    i386-softmmu/virtio-serial-bus.o
>    CC    i386-softmmu/virtio-scsi.o
>    CC    i386-softmmu/vhost_net.o
>    CC    i386-softmmu/kvm-stub.o
>    CC    i386-softmmu/vga.o
>    CC    i386-softmmu/memory.o
>    CC    i386-softmmu/savevm.o
>    CC    i386-softmmu/cputlb.o
>    CC    i386-softmmu/memory_mapping.o
>    CC    i386-softmmu/arch_memory_mapping.o
>    CC    i386-softmmu/arch_dump.o
>    CC    i386-softmmu/xen-stub.o
>    CC    i386-softmmu/device-hotplug.o
>    CC    i386-softmmu/exec.o
>    CC    i386-softmmu/translate-all.o
>    CC    i386-softmmu/cpu-exec.o
>    CC    i386-softmmu/translate.o
>    CC    i386-softmmu/tcg/tcg.o
>    CC    i386-softmmu/tcg/optimize.o
>    CC    i386-softmmu/fpu/softfloat.o
>    CC    i386-softmmu/op_helper.o
>    CC    i386-softmmu/helper.o
>    CC    i386-softmmu/cpu.o
>    CC    i386-softmmu/disas.o
>    CC    i386-softmmu/dump.o
> /home/buildbot/slave-spunk/fedora-mingw32/build/dump.c:17:24: fatal
> error: sys/procfs.h: No such file or directory
> compilation terminated.
> make[1]: *** [dump.o] Error 1
> make: *** [subdir-i386-softmmu] Error 2
>
> ========== full log ==========
> http://www.kraxel.org/bb/builders/fedora-mingw32/builds/130/steps/compile/logs/stdio
>
>

  reply	other threads:[~2012-06-07 11:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120607113054.BB1EF40244@spunk.home.kraxel.org>
2012-06-07 11:47 ` [Qemu-devel] Fwd: buildbot failure in qemu on fedora-mingw32 Gerd Hoffmann
2012-06-07 11:54   ` Anthony Liguori [this message]
2012-06-07 13:51     ` Stefan Weil
2012-06-11  2:02       ` Wen Congyang
     [not found] <20121118215508.9F6DD40296@spunk.home.kraxel.org>
2012-11-19  8:09 ` 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=4FD09684.5070604@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kraxel@gmail.com \
    --cc=lcapitulino@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).