From: Stefan Hajnoczi <stefanha@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Build break in current -git.
Date: Mon, 27 Jun 2011 14:48:02 +0100 [thread overview]
Message-ID: <BANLkTikOPKDJUgianXcBbVf5fs7A2wGHiw@mail.gmail.com> (raw)
In-Reply-To: <4E087836.8000508@landley.net>
On Mon, Jun 27, 2011 at 1:31 PM, Rob Landley <rob@landley.net> wrote:
> In file included from /usr/include/png.h:510,
> from ui/vnc-enc-tight.c:37:
> /usr/include/pngconf.h:371: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘.’ token
> /usr/include/pngconf.h:372: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘include’
> make: *** [ui/vnc-enc-tight.o] Error 1
>
> Building on an Ubuntu 10.04 stock install.
Yep, the buildbot sent out a bunch of emails about this breakage.
Stefan Weil has posted a patch to fix it:
http://patchwork.ozlabs.org/patch/102108/
Stefan
prev parent reply other threads:[~2011-06-27 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 12:31 [Qemu-devel] Build break in current -git Rob Landley
2011-06-27 13:48 ` Stefan Hajnoczi [this message]
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=BANLkTikOPKDJUgianXcBbVf5fs7A2wGHiw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).