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
Date: Thu, 7 Apr 2005 10:43:17 -0500
From: Brian Ford <ford AT vss DOT fsi DOT com>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: libnet-pcap-perl ??
In-Reply-To: <4254307A.93651604@dessent.net>
Message-ID: <Pine.CYG.4.58.0504071033341.3196@fordpc.vss.fsi.com>
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> <4254307A DOT 93651604 AT dessent DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-OriginalArrivalTime: 07 Apr 2005 15:43:23.0710 (UTC) FILETIME=[883B35E0:01C53B88]

On Wed, 6 Apr 2005, Brian Dessent wrote:

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

Sorry.  I forgot that I'm actually using LoadLibrary here.  But,

$ cygcheck ./wpcap.dll
.\wpcap.dll
  .\KERNEL32.dll
    .\ntdll.dll
  .\WSOCK32.dll
    .\WS2_32.dll
      .\msvcrt.dll
      .\WS2HELP.dll
        .\ADVAPI32.dll
          .\RPCRT4.dll
  .\pthreadVC.dll
  .\packet.dll
    .\USER32.dll
      .\GDI32.dll

So the dependency comes from winsock?  It doesn't sound like that is
avoidable?  That pthreadVC.dll is a bit scary too.

Also, the app in question uses a tiny portion of the ddraw.dll, which also
depends on msvcrt.dll.  I can't believe *this* is really not supported.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

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