From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: Julien Grall <julien.grall@citrix.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu@buildbot.b1-systems.de
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_i386_rhel61
Date: Sat, 12 Jan 2013 00:47:38 +0100 [thread overview]
Message-ID: <50F0A49A.6030702@suse.de> (raw)
In-Reply-To: <20130111220612.8416245A76@buildbot.b1-systems.de>
Am 11.01.2013 23:06, schrieb qemu@buildbot.b1-systems.de:
> The Buildbot has detected a new failure on builder default_i386_rhel61 while building qemu.
> Full details are available at:
> http://buildbot.b1-systems.de/qemu/builders/default_i386_rhel61/builds/483
>
> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>
> Buildslave for this Build: kraxel_rhel61_32bit
>
> Build Reason: The Nightly scheduler named 'nightly_default' triggered this build
> Build Source Stamp: [branch master] HEAD
> Blamelist:
>
> BUILD FAILED: failed compile
This is the expected i386 build failure due to lack of ULL:
CC i386-softmmu/hw/i386/../pc.o
cc1: warnings being treated as errors
/home/buildbot/slave-public/default_i386_rhel61/build/hw/i386/../pc.c:
In function 'ioport80_read':
/home/buildbot/slave-public/default_i386_rhel61/build/hw/i386/../pc.c:108:
error: integer constant is too large for 'long' type
/home/buildbot/slave-public/default_i386_rhel61/build/hw/i386/../pc.c:
In function 'ioportF0_read':
/home/buildbot/slave-public/default_i386_rhel61/build/hw/i386/../pc.c:133:
error: integer constant is too large for 'long' type
make[1]: *** [hw/i386/../pc.o] Error 1
make: *** [subdir-i386-softmmu] Error 2
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-01-11 23:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 22:06 [Qemu-devel] buildbot failure in qemu on default_i386_rhel61 qemu
2013-01-11 23:47 ` Andreas Färber [this message]
2013-01-12 0:40 ` Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2012-10-04 23:49 qemu
2012-09-17 23:48 qemu
2012-09-13 23:47 qemu
2012-07-09 23:06 qemu
2012-07-02 23:43 qemu
2012-05-15 1:03 qemu
2012-05-15 1:23 ` Anthony Liguori
2012-05-15 4:55 ` Daniel Gollub
2012-05-15 6:48 ` Gerd Hoffmann
2012-03-15 0:12 qemu
2012-02-04 0:06 qemu
2011-10-08 23:08 qemu
2011-10-03 23:13 qemu
2011-09-30 23:04 qemu
2011-08-29 23:03 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=50F0A49A.6030702@suse.de \
--to=afaerber@suse.de \
--cc=julien.grall@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu@buildbot.b1-systems.de \
--cc=stefanha@gmail.com \
/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.