On Jun 25, 2017, at 6:27 PM, Alan Partis wrote:
> On Sun, 25 Jun 2017, Guy Harris wrote:
>
>> On Jun 25, 2017, at 5:29 PM, Alan Partis wrote:
>>
>>> $ list zlib*
>>> Last metadata expiration check: 10:52:36 ago on Sat Jun 24 22:28:29 2017.
>>> Installed Packages
>>> zlib.i686
ubject: Re: [Wireshark-dev] linux package requirements for wireshark build
On Sat, Jun 24, 2017 at 11:11 PM, Alan Partis
mailto:alpar...@thundernet.com>> wrote:
I've looked through the wireshark developer's guide, and google'd all
around, but cannot find a list of required packa
On Sat, Jun 24, 2017 at 11:11 PM, Alan Partis
wrote:
> I've looked through the wireshark developer's guide, and google'd all
> around, but cannot find a list of required packages for building
> wireshark. If there is one, let me know.
I generally just run `tools/install_rpms_for_devel.sh` to i
On Jun 25, 2017, at 5:29 PM, Alan Partis wrote:
> $ dnf list zlib*
> Last metadata expiration check: 10:52:36 ago on Sat Jun 24 22:28:29 2017.
> Installed Packages
> zlib.i6861.2.8-10.fc24@fedora
> zlib.x86_64 1.2.8-10.fc24@koji
On Sun, 25 Jun 2017, Guy Harris wrote:
> On Jun 25, 2017, at 6:28 AM, Alan Partis wrote:
>
> > Yes, this _particular_ problem is because I had both i686 and x86_64
> > versions of the zlib package installed ... _and_ was missing zlib-devel.
>
> If you didn't have *any* zlib-devl packages install
On Jun 25, 2017, at 6:28 AM, Alan Partis wrote:
> Yes, this _particular_ problem is because I had both i686 and x86_64
> versions of the zlib package installed ... _and_ was missing zlib-devel.
If you didn't have *any* zlib-devl packages installed, it should've decided
zlib wasn't available, a
Yes, this _particular_ problem is because I had both i686 and x86_64
versions of the zlib package installed ... _and_ was missing zlib-devel.
Now I'm running into other problems after that in the build, but I'm still
pretty convinced they're package issues. I think this Fedora24 system is
a tad
On Sat, 24 Jun 2017, Guy Harris wrote:
> > One of the lines of output from ./configure is:
> >
> > "checking for inet_ntop... no"
> >
> > One the Fedora 25 system, where I'm successful with the build, it says:
> >
> > "checking for inet_ntop... yes"
>
> So, if you look for that test in the config
On Jun 24, 2017, at 8:11 PM, Alan Partis wrote:
> I'm running ./configure.
autoconf scripts write out, for debugging purposes, a "config.log" file.
> One of the lines of output from ./configure is:
>
> "checking for inet_ntop... no"
>
> One the Fedora 25 system, where I'm successful with the
I'm running ./configure. One of the lines of output from ./configure is:
"checking for inet_ntop... no"
One the Fedora 25 system, where I'm successful with the build, it says:
"checking for inet_ntop... yes"
But you're right, I had grep'd through the scripts and mistakenly thought
I was look
On Jun 24, 2017, at 11:31 AM, Alan Partis wrote:
> For clarity, the problem I'm seeing, I think, is that the ./configure
> script fails the CheckFunctionExists check
CheckFunctionExists is a CMake function; it's used in ConfigureChecks.cmake.
./configure is an autoconf script; CMake and autoco
For clarity, the problem I'm seeing, I think, is that the ./configure
script fails the CheckFunctionExists check for "inet_ntop" on the Fedora
24 system, but succeeds on my Fedora 25 system. However, on both systems,
the arpa/inet.h header is there.
On Sat, 24 Jun 2017, Alan Partis wrote:
> I
I have built the wireshark binary in the past on a Fedora 20 system and
more recently on a Fedora 25 system. Not entirely w/o struggles to ensure
the correct libraries/packages are present, but have still been successful
in the long run.
Today I'm trying it on a Fedora 24 system and I'm running i
13 matches
Mail list logo
