Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: [Wireshark-dev] Is anyone looking at current build breakage?

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: "Martin Mathieson" <martin.r.mathieson@xxxxxxxxxxxxxx>
Date: Thu, 1 Feb 2007 10:47:02 +0000

This is the end of the Windows buildbot log, very similar to my linux
build failure (I build with libpcap support enabled).

I don't have time to dig into it this morning...
Martin

Linking wireshark.exe
	link @C:\DOCUME~1\buildbot\LOCALS~1\Temp\nma02516.
ringbuffer.obj : error LNK2001: unresolved external symbol _libpcap_fdopen
ringbuffer.obj : error LNK2001: unresolved external symbol _libpcap_dump_close
wireshark.exe : fatal error LNK1120: 2 unresolved externals

  • Prev by Date: [Wireshark-dev] [Patch] SCSI persistent reserve in - service action
  • Next by Date: Re: [Wireshark-dev] Dissector for Cisco ITP packet logging facility
  • Previous by thread: Re: [Wireshark-dev] [Patch] SCSI persistent reserve in - service action
  • Next by thread: Re: [Wireshark-dev] Is anyone looking at current build breakage?
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation