Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <4254307A.93651604@dessent.net>
Date: Wed, 06 Apr 2005 11:54:50 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: libnet-pcap-perl ??
References: <d2v3hp$qef$1 AT sea DOT gmane DOT org> <42533B40 DOT A8382720 AT dessent DOT net> <Pine DOT CYG DOT 4 DOT 58 DOT 0504061329110 DOT 3196 AT fordpc DOT vss DOT fsi DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Brian Ford wrote:

> > The problem with all this is that the winpcap DLLs are compiled with
> > Mingw and depend on msvcrt, so if you want to use them with Cygwin apps
> > you have to recompile them to use cygwin1.dll.  If you don't do this,
> > the libpcap application (Net::Pcap in this case) will compile but fail
> > to run correctly.
> 
> Just curious what this really means.  I use the winpcap DLLs daily in a
> Cygwin appliction (custom, not Perl) without incident.  Am I just lucky?

I'm not entirely sure either. :-)  I too have "fudged it" and gotten
some apps to work, but with strage behavior sometimes.  Run cygcheck on
the app and see if it's loading both cygwin1.dll and msvcr*.dll, if so
then it's luck.  I think it mostly tends to work because the winpcap
stuff doesn't call the C runtime for much.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/