qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Consul <void@aleksoft.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Add pcap-based host network bridge
Date: Tue, 09 Jun 2009 14:49:26 -0700	[thread overview]
Message-ID: <h0mld6$o3f$1@ger.gmane.org> (raw)
In-Reply-To: <1BAB41F587B54E748B6A04352B27A1E9@FSCPC>

Sebastian Herbszt wrote:
> Consul wrote:
>> This small patch was needed to compile it. Otherwise it appears to 
>> work...
> 
> Odd. It compiles here fine. Can you post the error please?
> Which wpdpack version are you using?
> 

   CC    net.o
In file included from net.c:99:
c:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/remote-ext.h:39:2: #error Please do not include this file directly. Just define HAVE_REMOTE and then include pcap.h
In file included from qemu-common.h:74,
                  from net.c:120:
osdep.h:56:1: warning: "inline" redefined
In file included from c:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/pcap/pcap.h:41,
                  from c:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/pcap.h:45,
                  from net.c:97:
c:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/pcap-stdinc.h:66:1: warning: this is the location of the previous definition
net.c: In function `pcap_cleanup':
net.c:1236: warning: implicit declaration of function `pcap_getevent'
net.c:1236: warning: assignment makes pointer from integer without a cast
net.c:1237: warning: assignment makes pointer from integer without a cast
net.c: In function `net_pcap_init':
net.c:1236: warning: redundant redeclaration of 'pcap_getevent'
net.c:1236: warning: previous implicit declaration of 'pcap_getevent' was here
net.c:1422: warning: assignment makes pointer from integer without a cast
net.c:1423: warning: assignment makes pointer from integer without a cast

  reply	other threads:[~2009-06-09 21:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18  9:33 [Qemu-devel] [PATCH] Add pcap-based host network bridge Jan Kiszka
2009-03-22 20:38 ` Robert Riebisch
2009-03-22 21:38 ` [Qemu-devel] " Sebastian Herbszt
2009-03-24 17:21   ` Jan Kiszka
2009-03-23  2:23 ` [Qemu-devel] " Anthony Liguori
2009-03-24 17:28   ` [Qemu-devel] " Jan Kiszka
2009-03-28 17:26     ` Anthony Liguori
2009-05-11 21:30       ` [Qemu-devel] " Sebastian Herbszt
2009-05-12  8:23         ` [Qemu-devel] " Jan Kiszka
2009-05-12 15:48           ` Lennart Sorensen
2009-05-12 16:34             ` Jan Kiszka
2009-05-12 17:09               ` Lennart Sorensen
2009-05-12 21:45             ` Paul Brook
2009-05-12 21:17           ` Sebastian Herbszt
2009-05-20 17:43             ` Consul
2009-05-28 20:50               ` Sebastian Herbszt
2009-05-28 21:52                 ` Consul
2009-06-06 17:13                   ` Sebastian Herbszt
2009-06-06 18:40                     ` Alex
2009-06-08 21:27                       ` Consul
2009-06-09 20:13                         ` Sebastian Herbszt
2009-06-09 21:49                           ` Consul [this message]
2009-06-10 21:39                             ` Sebastian Herbszt

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='h0mld6$o3f$1@ger.gmane.org' \
    --to=void@aleksoft.net \
    --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).