I can not install the PKP package under Windows 7 (64bit). Does anyone know this?
Error message if I run "cabal install pcap":
cabal.exe: Continuous dependency on a foreign library:
- unavailable (or Bad file header: pcap.h
- Unavailable c library: PPP
I downloaded WinPcap 4.1.2 Developers Pack from here:
Tried both the installed Mengu / MSYS Scratch: prepackaged GHC 7-6.2 (ghc-7.6.2-x86_64-unknown-mingw32.tar.bz2) and compiled it under the Minig / MSYS.
There are many problems:
-
When I provide, the path to pcap.h (--extra-include-dirs) is included, Cabal configure ", but it fails on" cabil build "with" netbet "/in.h". "
-
If I have MSYS" Mingw-get msys-core-dev ", then installing netinet / in.h, I'm getting different types of tones already defined messages < Li>
is not libpcap.a in the WinPCap developers pack (this libwpcap .a) and it seems that its not a 64 bit version. I need to compile myself?
I would appreciate it if anyone could suggest that Windows Under normal circumstances, how is such a situation governed for cable packages?
The WinPCap developers pack does not have libpcap.a (this is libwpcap.a).
Correct. For better or worse, while the library is called "libpcap" on UN * X, Au Thus, the flag is linked to
-lpcap , it is called "WinPcap" on Windows and the
.a file is called "libwpcap.a", which means that if If you create an app with UN * X-style tool, it will be linked to flag
-lwpcap . No, even if you're using UN * X-style files on Windows, you do not use the same flag to link to a PAP-based program, Do it on X.
And, yes, you have to compile yourself 64-bit versions; While they provide a 64-bit version of the
.lib file for use with Microsoft Construction Tools, they do not appear to offer the 64-bit version of
.a UN * X-like files for the use of the file.
-
No comments:
Post a Comment