Wireshark-dev: Re: [Wireshark-dev] Building Wireshark on SuSE 11.4 fails, configure does not fi
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Thu, 12 Oct 2017 10:21:53 -0700
On Oct 12, 2017, at 4:02 AM, João Valverde <joao.valverde@xxxxxxxxxxxxxxxxxx> wrote:

> On 12-10-2017 11:25, Anders Broman wrote:
>>> 
>>> Is this a built from a git checkout or from a release tarball?  If it's from a git checkout, what happens if you do a "make maintainer-clean", a "./autogen.sh", and then a >"./configure"?
>> It's from an svn clone of the old svn repo kept up to date with the latest git version. I did check a fresh svn checkout. I could try to build the standard Wireshark
>> From trunk.
> 
> Probably related to https://code.wireshark.org/review/#/c/23329/.
> 
> The problem still needs to be investigated, the autoconf macro is complex and impossible to test for all platforms and libpcap versions.

The comment in your change says

	    # We have pcap-config; we assume that means we have libpcap
	    # installed and that pcap-config will tell us whatever
	    # libraries libpcap needs.

As the creator of pcap-config, I can state unequivocally that if that assumption is incorrect, that would indicate that the pcap-config on the machine in question is buggy.  Whether the bug is the fault of tcpdump.org or of the platform on the machine is another matter.

Anders, what does running

	pcap-config --libs

and

	pcap-config --libs --static

on the SuSE and Ubuntu machines print?