qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, gollub@b1-systems.de,
	qemu@buildbot.b1-systems.de, agraf@suse.de,
	lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_mingw32
Date: Tue, 30 Oct 2012 16:05:45 +0200	[thread overview]
Message-ID: <20121030140545.GA27913@redhat.com> (raw)
In-Reply-To: <508F89BA.5090907@redhat.com>

On Tue, Oct 30, 2012 at 09:03:06AM +0100, Paolo Bonzini wrote:
> Il 30/10/2012 01:53, qemu@buildbot.b1-systems.de ha scritto:
> > The Buildbot has detected a new failure on builder default_mingw32 while building qemu.
> > Full details are available at:
> >  http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/420
> > 
> > Buildbot URL: http://buildbot.b1-systems.de/qemu/
> > 
> > Buildslave for this Build: kraxel_rhel61
> > 
> > Build Reason: The Nightly scheduler named 'nightly_default' triggered this build
> > Build Source Stamp: [branch master] HEAD
> > Blamelist: 
> > 
> > BUILD FAILED: failed compile
> > 
> > sincerely,
> >  -The Buildbot
> > 
> 
> Michael, this is yours:
> 
>   LINK  i386-softmmu/qemu-system-i386.exe
> hw/virtio-net.o:virtio-net.c:(.text+0xbe0): undefined reference to `tap_has_vnet_hdr_len'
> hw/virtio-net.o:virtio-net.c:(.text+0xbfc): undefined reference to `tap_set_vnet_hdr_len'
> make[1]: *** [qemu-system-i386.exe] Error 1
> make: *** [subdir-i386-softmmu] Error 2

Fixed, thanks for the report.

  reply	other threads:[~2012-10-30 14:03 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30  0:53 [Qemu-devel] buildbot failure in qemu on default_mingw32 qemu
2012-10-30  8:03 ` Paolo Bonzini
2012-10-30 14:05   ` Michael S. Tsirkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-18 22:27 qemu
2013-01-14 22:23 qemu
2013-01-03 22:51 qemu
2012-11-16 22:48 qemu
2012-11-17  7:28 ` Stefan Weil
2012-11-03  1:11 qemu
2012-11-03  6:08 ` Stefan Hajnoczi
2012-11-03  9:24   ` Daniel Gollub
2012-11-03 14:35     ` Stefan Hajnoczi
2012-10-05 23:51 qemu
2012-10-08  6:07 ` Stefan Hajnoczi
2012-09-10 23:54 qemu
2012-09-11  5:14 ` Stefan Weil
2012-09-11  5:23   ` Stefan Weil
2012-09-11  6:57     ` Paolo Bonzini
2012-09-11  7:05   ` Zhang, Yang Z
2012-09-11  7:07     ` Paolo Bonzini
2012-09-11  7:15       ` Zhang, Yang Z
2012-09-06  0:06 qemu
2012-09-06  0:22 ` Max Filippov
2012-08-14 23:32 qemu
2012-08-06 23:26 qemu
2012-08-03 23:29 qemu
2012-07-19 23:18 qemu
2012-07-17 23:10 qemu
2012-07-09 23:47 qemu
2012-03-15  0:32 qemu
2012-03-01  0:36 qemu
2012-03-01  0:35 ` Roy Tam
2012-02-04  0:11 qemu
2012-02-03 23:43 ` Anthony Liguori
2012-02-04  8:29   ` Stefan Weil
2012-02-06 20:27     ` Corey Bryant
2012-02-07 10:28       ` Stefan Hajnoczi
2012-02-07 14:32         ` Corey Bryant
2012-02-07 14:59           ` Stefan Hajnoczi
2012-02-07 15:10             ` Corey Bryant
2011-12-13  1:02 qemu
2011-12-13  6:33 ` Paolo Bonzini
2011-10-03 23:29 qemu
2011-09-30 23:06 qemu
2011-09-20 23:28 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=20121030140545.GA27913@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=gollub@b1-systems.de \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@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).