From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9VX failure
Date: Sat, 11 Sep 2010 13:46:16 -0400 [thread overview]
Message-ID: <AANLkTi=q_u3iCwx=7jzrHM=H2jNxodMFBEsBWQBcXkvk@mail.gmail.com> (raw)
In-Reply-To: <20100911173801.GF4113@fangle.proxima.alt.za>
pcap is for the virtual ethernet driver to use the native ip stack.
there's another one that uses TAP that yiyus finalized from someone
else's efforts (I'm not giving due credit here, sorry). If you don't
have pcap just don't build etherve.c.
--dho
2010/9/11 Lucio De Re <lucio@proxima.alt.za>:
> On Sat, Sep 11, 2010 at 10:24:05AM -0700, ron minnich wrote:
>> >>
>> > Is that included in rminnich/vx32, where default compilation fails with
>> > a missing "pcap.h"?
>>
>> the pcap.h thing is unrelated and I think I'm going to change it so
>> that it builds default with no pcap support, since I'm not the only
>> person seeing this build error.
>>
>> no, I have to get his patch included. I had a question in to his
>> customer support people about the patch first before i went with the
>> patch :-)
>>
> That means that there are two patches required here: Charles' adjustment
> (why have I not seen it, I wonder) and the pcap.h thing. Can you post
> them here in the interim? I'm not sure I want to know why pcap.h is
> being included and not found...
>
> ++L
>
>
next prev parent reply other threads:[~2010-09-11 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 7:02 Lucio De Re
2010-09-11 7:14 ` Lucio De Re
2010-09-11 16:34 ` ron minnich
2010-09-11 17:18 ` Lucio De Re
2010-09-11 17:24 ` ron minnich
2010-09-11 17:38 ` Lucio De Re
2010-09-11 17:46 ` Devon H. O'Dell [this message]
2010-09-11 18:14 ` Lucio De Re
2010-09-11 19:02 ` yy
2010-09-11 20:25 ` ron minnich
2010-09-11 20:25 ` ron minnich
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='AANLkTi=q_u3iCwx=7jzrHM=H2jNxodMFBEsBWQBcXkvk@mail.gmail.com' \
--to=devon.odell@gmail.com \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).