From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: libnet on cygwin: how to deal with libpcap?
Date: Sat, 16 Dec 2017 02:08:00 -0000 [thread overview]
Message-ID: <e97d3763-fc20-18f2-8cc1-8bfc47ba6c9b@SystematicSw.ab.ca> (raw)
In-Reply-To: <1513349633.2925.2.camel@gmx.net>
On 2017-12-15 07:53, Gianpaolo Pedrazza wrote:
> On gio, 2017-12-14 at 16:19 -0700, Brian Inglis wrote:
>> On 2017-12-14 12:32, Gianpaolo Pedrazza wrote:
>>>
>>> On mar, 2017-12-12 at 09:07 -0700, Brian Inglis wrote:
>>> I had a look, but I couldn't do too much and decided to go through
>>> another way. Apparently there is a patch that can be applied to the
>>> libnet source files before compiling the library under cygwin. It
>>> was
>>> once available under http://mathieu.carbou.free.fr/pub/libnet/1.1.2
>>> .1/l
>>> ibnet-cygwin-diffs-1.1.2.1.zip. Is anyone here who has downloaded
>>> this
>>> zip file or knows where a copy is available on the link?
>> Google URL gives the patch in
>> https://marc.info/?l=libnet&m=109157113801801
>> This patch may need further updates.
> Unfortunately is this link also broken, however marc.info redirects to
> the homepage of Mathieu Carbou, the guy who developed the patch. I will
> write directly to him. Thank you.
I can access that page without any problems?!
It contains the acinclude.m4 patch as a diff and the patched acinclude.m4.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-12-16 1:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 13:04 Gianpaolo Pedrazza
2017-12-12 19:42 ` Brian Inglis
2017-12-14 19:57 ` Gianpaolo Pedrazza
2017-12-15 0:33 ` Brian Inglis
2017-12-16 1:32 ` Gianpaolo Pedrazza
2017-12-16 2:08 ` Brian Inglis [this message]
2017-12-18 17:27 ` Gianpaolo Pedrazza
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=e97d3763-fc20-18f2-8cc1-8bfc47ba6c9b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).