On 12 October 2016 at 20:15, Evan Huus <[email protected]> wrote: > On Wed, Oct 12, 2016 at 3:04 PM, Guy Harris <[email protected]> wrote: > > On Oct 12, 2016, at 11:41 AM, Jeff Morriss <[email protected]> > wrote: > > > >> Just for fun I did a quick search for that Usage output (minus the > "Wireshark" prefix which is clearly $0) and found this program which has > that exact output: > >> > >> https://github.com/the-tcpdump-group/libpcap/blob/ > master/tests/capturetest.c > > > > Yeah, that's one of a pile of test programs I wrote to test various > libpcap features. > > > > The binary is *not* part of a libpcap installation, so there shouldn't > be an executable for it unless the test programs were built. > > > > Evan, what happens if you remove the build directory entirely, re-create > it, do a cmake in it, and then redo the build? > > Completely blowing away the build directory and starting again seems > to have fixed it. That was really weird, especially since (to my > knowledge) I don't even have a source build of libpcap on this > machine. > > Anywho, thanks everyone for the help! > > CMake standard repair #1 :-)
-- Graham Bloice
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
