qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Stefan Weil <weil@mail.berlios.de>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] buildbot failure in qemu on block_mingw32
Date: Thu, 10 Jan 2013 13:44:22 +0100	[thread overview]
Message-ID: <20130110124422.GF30946@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <495746080bc52c7893ee32b86f105d4f.squirrel@weilnetz.de>

On Wed, Jan 09, 2013 at 06:16:01PM +0100, Stefan Weil wrote:
> > On Tue, Jan 08, 2013 at 01:06:19AM +0100, qemu@buildbot.b1-systems.de
> > wrote:
> >> 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/439
> >>
> >> Buildbot URL: http://buildbot.b1-systems.de/qemu/
> >>
> >> Buildslave for this Build: kraxel_rhel61
> >
> > Here is the error:
> >
> > /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/savevm.c: In function
> > 'do_savevm':
> > /home/buildbot/slave-public/block_mingw32/build/savevm.c:2097: error:
> > storage size of 'tb' isn't known
> > /home/buildbot/slave-public/block_mingw32/build/savevm.c:2133: warning:
> > implicit declaration of function '_ftime'
> > /home/buildbot/slave-public/block_mingw32/build/savevm.c:2133: warning:
> > nested extern declaration of '_ftime'
> > /home/buildbot/slave-public/block_mingw32/build/savevm.c:2097: warning:
> > unused variable 'tb'
> >
> > Stefan
> 
> 
> I don't get this error in line 2097 with my native and cross builds,
> nor do I get the warnings. Which version of MinGW is used on the buildbot?
> 
> Anyway, it will be fixed with the pending patch
> http://patchwork.ozlabs.org/patch/210240/

I've added Gerd on CC if he has time to check the buildbot.  But since
this will be fixed anyway it probably doesn't matter.

Stefan

  reply	other threads:[~2013-01-10 12:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  0:06 [Qemu-devel] buildbot failure in qemu on block_mingw32 qemu
2013-01-09  8:53 ` Stefan Hajnoczi
2013-01-09 17:16   ` Stefan Weil
2013-01-10 12:44     ` Stefan Hajnoczi [this message]
2013-01-10 13:08       ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2013-01-16  0:06 qemu
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-24  1:05 qemu
2012-10-24  9:16 ` Kevin Wolf
2012-10-24 11:39   ` Luiz Capitulino
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=20130110124422.GF30946@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    --cc=weil@mail.berlios.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).