From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] build error in current master
Date: Sun, 21 Mar 2010 14:17:09 -0500 [thread overview]
Message-ID: <4BA670B5.6010704@codemonkey.ws> (raw)
In-Reply-To: <f43fc5581003200114q34510a82g92dd6bbe4e6aeb14@mail.gmail.com>
On 03/20/2010 03:14 AM, Blue Swirl wrote:
> On 3/20/10, Paul Bolle<pebolle@tiscali.nl> wrote:
>
>> 0) Building current master (3290c4aac5b97bb1e3b2b28d94669f2c611ce84a,
>> Introduce a default qmp session) fails here:
>>
>> $ make> /dev/null
>> cc1: warnings being treated as errors
>> curses.c: In function ‘curses_display_init’:
>> curses.c:341: error: initialization from incompatible pointer type
>> make: *** [curses.o] Error 1
>>
>> 1) It seems caused by commit d7234f4d (committed half a day ago):
>>
>> $ git blame curses.c | grep 341
>> d7234f4d (Anthony Liguori 2010-03-17 17:59:26 -0500 341) static
>> Notifier notifier = { .notify = curses_atexit };
>>
>> $ git log -1 d7234f4d --pretty=short
>> commit d7234f4d7e373a708e1df9ab565a71b71b189025
>> Author: Anthony Liguori<aliguori@us.ibm.com>
>>
>> Convert atexit users to exit_notifier
>>
>> Regards,
>>
> Fixed in HEAD.
>
I've reverted a bunch of these commits. They're still a
work-in-progress. Looks like I pushed the wrong branch.
Sorry for the noise.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-03-21 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 7:47 [Qemu-devel] build error in current master Paul Bolle
2010-03-20 8:14 ` Blue Swirl
2010-03-21 19:10 ` Anthony Liguori
2010-03-21 19:17 ` Anthony Liguori [this message]
2010-03-21 19:37 ` Blue Swirl
2010-03-21 23:30 ` Anthony Liguori
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=4BA670B5.6010704@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=pebolle@tiscali.nl \
--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.