public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: libnet on cygwin: how to deal with libpcap?
Date: Tue, 12 Dec 2017 19:42:00 -0000	[thread overview]
Message-ID: <4fc60018-3b9b-1695-9975-2c2e9c8af8f5@SystematicSw.ab.ca> (raw)
In-Reply-To: <1513061645.3889.0.camel@gmx.net>

On 2017-12-11 23:54, Gianpaolo Pedrazza wrote:
> I need to install libnet and I found on various sites [2][3] that the
> only one way to install the prerequisite libpcap is to extract the
> Developer Pack [4] into cygwin. I did it, I run all the tests and the
> pcap library seemed to work pretty well. So I run the configure file
> the latest available version of libnet and I was able to create the
> Makefile. My problem comes running the "make" command, because the
> libpcap library includes winsock2.h while libnet is based on socket.h.
> Is this definitely an incompatibility between the two libraries or
> there is something which can be done? Does someone know another way to
> install libpcap on cygwin?

Might want to look at
http://www.win10pcap.org/ or
https://github.com/nmap/npcap/ from the nmap project, or both.

-- 
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

  reply	other threads:[~2017-12-12 16:07 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 [this message]
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
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=4fc60018-3b9b-1695-9975-2c2e9c8af8f5@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).