Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Where is libpcap-devel source code.

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Fri, 11 May 2007 10:41:53 -0700
John wrote:

Near as I can tell, my Solaris 10 x86 system needs libpcap-devel, compiled from source, in order for wireshark to build:

No, it needs a development version of libpcap to build versions of Wireshark *OR* TShark that can capture packets. It can build versions of TShark *AND* Wireshark without libpcap, but those versions would only be able to read and dissect existing capture files - they wouldn't be able to capture traffic.

It needs GTK+ to build Wireshark, but it doesn't need it to build TShark.

                   Use pcap library : yes

It appears to have found libpcap.

I cannot seem to find the source code for "libpcap-devel", only the RPM?

If you found an RPM, you might be looking in the wrong place, unless people are packaging up source for non-Linux systems in RPMs. The source code for libpcap can be downloaded from

	http://www.tcpdump.org/

and if you build and install it, you get the header files and libraries you need to build programs with libpcap. (There's no "libpcap-devel" on www.tcpdump.org - the split between "libpcap" and "libpcap-devel" is a characteristic of binary packages for libpcap, so that if you want to run programs that use a libpcap shared library, but don't need to build programs that use libpcap, you can just install "libpcap" without also installing "libpcap-devel".)

However, as it appears you already have libpcap - complete with the header files, so you have the development stuff installed - so don't spend any more time worrying about libpcap.

Instead, worry about GTK+:

Additional "configure" information, which may, or may not(?) be helpful:

checking for GTK+ - version >= 2.0.0... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GTK+ is incorrectly installed.

It's *very* helpful - it shows that the problem is that the configure script couldn't find GTK+.

What does the file "config.log" say about GTK+? That file should be in the top-level source directory for Wireshark.