From: Wen Congyang <wency@cn.fujitsu.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Gerd Hoffmann <kraxel@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Fwd: buildbot failure in qemu on fedora-mingw32
Date: Mon, 11 Jun 2012 10:02:03 +0800 [thread overview]
Message-ID: <4FD5519B.3020000@cn.fujitsu.com> (raw)
In-Reply-To: <4FD0B1FA.30508@weilnetz.de>
At 06/07/2012 09:51 PM, Stefan Weil Wrote:
> Am 07.06.2012 13:54, schrieb Anthony Liguori:
>> Luiz/Wen Congyang: ^
>>
>> Regards,
>>
>> Anthony Liguori
>> /home/buildbot/slave-spunk/fedora-mingw32/build/dump.c:17:24: fatal
>
> It looks like sys/procfs.h is not needed at all.
> I just sent a patch which removes this and some more include statements.
>
> Anthony, as this is a build fix, I won't send a pull request.
> Please take the patch as it is (if nobody minds).
>
> Wen, dump.c and dump.h both use a wrong license.
> Would you mind changing it to GPL2+?
I copy it from the other file in qemu, but it is OK to change it to GPL2+.
Thanks
Wen Congyang
>
> Regards,
>
> Stefan W.
>
>>> error: sys/procfs.h: No such file or directory
>>> compilation terminated.
>>> make[1]: *** [dump.o] Error 1
>>> make: *** [subdir-i386-softmmu] Error 2
>>>
>>> ========== full log ==========
>>> http://www.kraxel.org/bb/builders/fedora-mingw32/builds/130/steps/compile/logs/stdio
>>>
>>>
>>>
>>
>>
>
>
next prev parent reply other threads:[~2012-06-11 2:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120607113054.BB1EF40244@spunk.home.kraxel.org>
2012-06-07 11:47 ` [Qemu-devel] Fwd: buildbot failure in qemu on fedora-mingw32 Gerd Hoffmann
2012-06-07 11:54 ` Anthony Liguori
2012-06-07 13:51 ` Stefan Weil
2012-06-11 2:02 ` Wen Congyang [this message]
[not found] <20121118215508.9F6DD40296@spunk.home.kraxel.org>
2012-11-19 8:09 ` Gerd Hoffmann
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=4FD5519B.3020000@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=anthony@codemonkey.ws \
--cc=kraxel@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).