From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel@nongnu.org, gollub@b1-systems.de, agraf@suse.de,
lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_mingw32
Date: Sat, 17 Nov 2012 08:28:56 +0100 [thread overview]
Message-ID: <50A73CB8.5060709@weilnetz.de> (raw)
In-Reply-To: <20121116224832.0CE2841A2E@buildbot.b1-systems.de>
Am 16.11.2012 23:48, schrieb qemu@buildbot.b1-systems.de:
> 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/438
>
> 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
>
Anthony, is this code needed for MinGW?
backends/rng-random.c: In function 'rng_random_opened':
backends/rng-random.c:77: error: 'O_NONBLOCK' undeclared (first use in this function)
backends/rng-random.c:77: error: (Each undeclared identifier is reported only once
backends/rng-random.c:77: error: for each function it appears in.)
Regards
Stefan W.
next prev parent reply other threads:[~2012-11-17 7:29 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 22:48 [Qemu-devel] buildbot failure in qemu on default_mingw32 qemu
2012-11-17 7:28 ` Stefan Weil [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-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-30 0:53 qemu
2012-10-30 8:03 ` Paolo Bonzini
2012-10-30 14:05 ` Michael S. Tsirkin
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=50A73CB8.5060709@weilnetz.de \
--to=sw@weilnetz.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=gollub@b1-systems.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.