qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/5] Redirect slirp traffic to/from qemu character device.
Date: Wed, 07 Jan 2009 10:52:49 -0600	[thread overview]
Message-ID: <4964DDE1.6040809@codemonkey.ws> (raw)
In-Reply-To: <20090105151504.3819.46080.stgit@dhcp-1-237.tlv.redhat.com>

Gleb Natapov wrote:
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> ---
>
>  slirp/libslirp.h |    5 ++-
>  slirp/main.h     |    1 +
>  slirp/misc.c     |    2 +
>  slirp/sbuf.c     |    2 +
>  slirp/slirp.c    |   62 +++++++++++++++++++++++++++++++++-
>  slirp/socket.c   |   99 +++++++++++++++++++++++++++++++++++++++++++-----------
>  slirp/socket.h   |    2 +
>  slirp/tcp_subr.c |    5 +++
>  8 files changed, 154 insertions(+), 24 deletions(-)
>
>   

This patch breaks the Windows build.

In file included from /home/anthony/svn/qemu/slirp/slirp.h:215,
                 from /home/anthony/svn/qemu/slirp/slirp.c:24:
/home/anthony/svn/qemu/slirp/socket.h:90: warning: 'struct iovec' 
declared inside parameter list
/home/anthony/svn/qemu/slirp/socket.h:90: warning: its scope is only 
this definition or declaration, which is probably not what you want
/home/anthony/svn/qemu/slirp/slirp.c: In function 'slirp_select_poll':
/home/anthony/svn/qemu/slirp/slirp.c:458: warning: passing argument 2 of 
'send' from incompatible pointer type
/home/anthony/svn/qemu/slirp/slirp.c: In function 'slirp_send':
/home/anthony/svn/qemu/slirp/slirp.c:749: warning: implicit declaration 
of function 'qemu_chr_write'
/home/anthony/svn/qemu/slirp/slirp.c: In function 'slirp_socket_can_recv':
/home/anthony/svn/qemu/slirp/slirp.c:774: error: array type has 
incomplete element type
/home/anthony/svn/qemu/slirp/slirp.c:774: warning: unused variable 'iov'
/home/anthony/svn/qemu/slirp/slirp.c: In function 'slirp_socket_recv':
/home/anthony/svn/qemu/slirp/slirp.c:800: warning: pointer targets in 
passing argument 2 of 'soreadbuf' differ in signedness


You probably need to add an #include to get our version of struct iovec 
for Windows.

Regards,

Anthony Liguori

  reply	other threads:[~2009-01-07 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 15:14 [Qemu-devel] [PATCH v2 0/5] Marry slirp and qemu character device Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 1/5] Redirect slirp traffic to/from " Gleb Natapov
2009-01-07 16:52   ` Anthony Liguori [this message]
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 2/5] Add vmchannel command line option Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 3/5] Add slirp_restrict option Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 4/5] Add "restrict" and "ip" option to "user" net option Gleb Natapov
2009-01-05 15:15 ` [Qemu-devel] [PATCH v2 5/5] Add support for vmchannel socket migration Gleb Natapov
2009-01-05 15:35 ` [Qemu-devel] [PATCH v2 0/5] Marry slirp and qemu character device Anthony Liguori
2009-01-05 16:21   ` Gleb Natapov
2009-01-05 15:38 ` 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=4964DDE1.6040809@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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 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).