output of 'wireshark -v': Copyright 1998-2016 Gerald Combs [email protected] and contributors. License GPLv2+: GNU GPL version 2 or later http://www.gnu.org/licenses/old-licenses/gpl-2.0.html This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled (64-bit) with Qt 5.3.2, with libpcap, without POSIX capabilities, with libz 1.2.5, with GLib 2.36.0, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, with GnuTLS 2.12.19, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with QtMultimedia, without AirPcap. Running on Mac OS X 10.11.6, build 15G31 (Darwin 15.6.0), with locale en_US.UTF-8, with libpcap version 1.5.3 - Apple version 54, with libz 1.2.5, with GnuTLS 2.12.19, with Gcrypt 1.5.0. Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (with SSE4.2) Built using llvm-gcc 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.9.00). When installing Wireshark from a .dmg file, the man pages are not populated. /usr/share/man/man1 does not contain a man page for Wireshark, nor can I use 'man wireshark'. I have confirmed that this is also an issue for other Mac users as it has been submitted as a bug found here. Considering that man pages worked for me on the Linux version of Wireshark, and not on the Mac version, and since it is occurring on other's Macs, I can confirm this as a minor bug. I made the assumption that the file is populated during Make, but I want to get more information here. How does Wireshark populate the man pages, and how could I fix this for Mac builds? asked 26 Aug '16, 18:39 xeno |
One Answer:
It depends. "make install" will typically install them in
Have the post-install script for the CLI, in the Wireshark install package for OS X, copy the man pages to That script is in the Wireshark source; it's The default answered 26 Aug '16, 19:21 Guy Harris ♦♦ |