I committed some of the modifications, but I'm not completely done. Some modifications have to be committed to the original libpcap repository, and I need to make sure not to break anything on the other platforms supported by libpcap.
Have a nice day GV -------------------------------------------------- From: "Alon Bar-Lev" <[email protected]> Sent: Wednesday, October 06, 2010 10:11 AM To: <[email protected]> Subject: Re: [Winpcap-users] 4.1.2 Compatibility with mingw-w64 toolchain? > What about [1]? > > [1] http://www.mail-archive.com/[email protected]/msg00750.html > > On Wed, Oct 6, 2010 at 6:53 PM, Gianluca Varenni > <[email protected]> wrote: >> >> >> -------------------------------------------------- >> From: "noreply" <[email protected]> >> Sent: Wednesday, October 06, 2010 9:40 AM >> To: <[email protected]> >> Subject: Re: [Winpcap-users] 4.1.2 Compatibility with mingw-w64 >> toolchain? >> >>> I have a solution to this problem. The short answer is that there is a >>> problem with the mingw-w64 toolchain, specifically in gcc's 'binutils' >>> which >>> generate the actual dynamic library. >>> >>> The reason it works for 32-bit version and not for 64-bit version is >>> that >>> wpdpack/lib directory contains the libpwpap.a file which gcc can link >>> against correctly, while the wpdpack/lib/x64 directory only contains the >>> wpcap.lib and no 64-bit libwpcap.a compatible library. Therefore, >>> because >>> of >>> the 'binutils' bug, the 64-bit builds fail against the .lib file alone. >>> >>> May be in the future releases, the WinPcap team can generate the >>> libwpcap.a >>> file as well for x64 architecture? >> >> The reason why so far we haven't generated a libwpcap.a for x64 is that >> we >> use cygwin for the generation of the *.a files, and cygwin (last time I >> checked) does not support x64 compilation. It should rather >> straightforward >> to migrate to mingw, it's just something that we haven't done yet. >> >> Have a nice day >> GV >> >> >>> >>> Here is a link to the the full discussion on this: >>> >>> https://sourceforge.net/projects/mingw-w64/forums/forum/723797/topic/3882579 >>> >>> Cheers, >>> mark... >>> >>>> -----Original Message----- >>>> From: [email protected] >>>> [mailto:[email protected]] On Behalf Of Mark >>>> Bednarczyk >>>> Sent: Wednesday, October 06, 2010 10:14 AM >>>> To: [email protected] >>>> Subject: [Winpcap-users] 4.1.2 Compatibility with mingw-w64 toolchain? >>>> >>>> Hi, >>>> I'm linking my code using mingw-w64 toolchain on Win7 >>>> x86_64 system. The code compiles against the WpdPack 4.1.2, >>>> wpcap in lib/x64 directory and links. Then at runtime all the >>>> pcap_* library calls are incorrectly linked again WinPcap >>>> 4.1.2 runtime install and core-dump immediately. >>>> >>>> Even this will coredump: >>>> >>>> const char *name = pcap_datalink_val_to_name(1); >>>> >>>> Has anyone tried using mingw-w64 to link their code with >>>> latest x64 pcap? >>>> >>>> Here is a little blog I'm keeping on this issue, until its >>>> resolved. It has a stack-trace: >>>> http://jnetpcap.com/node/662 >>>> >>>> Cheers, >>>> mark... >>>> http://jnetpcap.com >>>> >>>> >>>> _______________________________________________ >>>> Winpcap-users mailing list >>>> [email protected] >>>> https://www.winpcap.org/mailman/listinfo/winpcap-users >>>> >>> >>> >>> _______________________________________________ >>> Winpcap-users mailing list >>> [email protected] >>> https://www.winpcap.org/mailman/listinfo/winpcap-users >> >> _______________________________________________ >> Winpcap-users mailing list >> [email protected] >> https://www.winpcap.org/mailman/listinfo/winpcap-users >> > _______________________________________________ > Winpcap-users mailing list > [email protected] > https://www.winpcap.org/mailman/listinfo/winpcap-users > _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
