From: Stefan Weil <weil@mail.berlios.de>
To: Daniel Gollub <gollub@b1-systems.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] buildbot failure in qemu on disable_kvm_x86_64_debian_5_0
Date: Mon, 04 Jul 2011 07:51:41 +0200 [thread overview]
Message-ID: <4E1154ED.6020700@mail.berlios.de> (raw)
In-Reply-To: <CAJSP0QUuq-8v8uAYVodXx6uppoQXui4uhTs7vxug_Cpm-i67+w@mail.gmail.com>
Am 04.07.2011 06:23, schrieb Stefan Hajnoczi:
> On Mon, Jul 4, 2011 at 12:47 AM, Alexander Graf <agraf@suse.de> wrote:
>>
>> On 04.07.2011, at 02:04, qemu@buildbot.b1-systems.de wrote:
>>
>>> The Buildbot has detected a new failure on builder
>>> disable_kvm_x86_64_debian_5_0 while building qemu.
>>> Full details are available at:
>>> http://buildbot.b1-systems.de/qemu/builders/disable_kvm_x86_64_debian_5_0/builds/148
>>>
>>> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>>>
>>> Buildslave for this Build: b1_qemu_1
>>>
>>> Build Reason: The Nightly scheduler named 'nightly_disable_kvm'
>>> triggered this build
>>> Build Source Stamp: [branch master] HEAD
>>> Blamelist:
>>>
>>> BUILD FAILED: failed compile
>>
>> In file included from /usr/include/png.h:438,
>> from ui/vnc-enc-tight.c:40:
>> /usr/include/pngconf.h:326: error: expected '=', ',', ';', 'asm' or
>> '__attribute__' before '.' token
>> /usr/include/pngconf.h:327: error: expected '=', ',', ';', 'asm' or
>> '__attribute__' before 'include'
>> make: *** [ui/vnc-enc-tight.o] Error 1
>>
>> program finished with exit code 2
>>
>>
>> Not sure what exactly is missing, but the last change in that code
>> was from Stefan Weil (2fb0c09f4ff036f68474277ed4edc036f6529de8).
>
> Daniel,
> Would it be possible to post the contents of /usr/include/pngconf.h
> from b1_qemu_1? I checked my local copy and I don't understand these
> compiler errors. Perhaps you have a different version of the file.
>
> Thanks,
> Stefan
The compiler errors come again from the setjmp check in pngconf.h:
__pngconf.h__ in libpng already includes setjmp.h;
__dont__ include it again.;
The buildbot runs Debian Lenny which includes an old version of libpng.
That version does not use PNG_SKIP_SETJMP_CHECK to skip the setjmp check.
Defining PNG_SETJMP_NOT_SUPPORTED might help with this
version, but I still have to test that.
Updating the buildbot to Debian Squeeze would also work.
Cheers,
Stefan
next prev parent reply other threads:[~2011-07-04 5:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 0:04 [Qemu-devel] buildbot failure in qemu on disable_kvm_x86_64_debian_5_0 qemu
2011-07-03 23:47 ` Alexander Graf
2011-07-04 4:23 ` Stefan Hajnoczi
2011-07-04 5:41 ` Daniel Gollub
2011-07-04 6:08 ` Stefan Hajnoczi
2011-07-04 5:51 ` Stefan Weil [this message]
2011-07-04 9:21 ` Alexander Graf
2011-07-04 16:33 ` Stefan Weil
2011-07-04 18:44 ` [Qemu-devel] [PATCH] Remove unneeded setjmp.h (fix compilation with on Debian "lenny") Stefan Weil
2011-07-04 18:51 ` Stefan Weil
2011-07-04 18:52 ` [Qemu-devel] [PATCH v2] Remove unneeded setjmp.h (fix compilation " Stefan Weil
2011-07-04 21:02 ` Peter Maydell
2011-07-12 21:28 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2011-07-22 0:05 [Qemu-devel] buildbot failure in qemu on disable_kvm_x86_64_debian_5_0 qemu
2011-06-27 0: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=4E1154ED.6020700@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=agraf@suse.de \
--cc=gollub@b1-systems.de \
--cc=qemu-devel@nongnu.org \
--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 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).