Wireshark-dev: Re: [Wireshark-dev] Problem compiling Wireshark 1.6.1
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Gerald Combs <gerald@xxxxxxxxxxxxx>
Date: Mon, 29 Aug 2011 12:27:03 -0700
On 8/29/11 11:18 AM, Guy Harris wrote:
> 
> On Aug 27, 2011, at 10:58 PM, Helge Kruse wrote:
> 
>> What program package is EVAR, never heard about it.
> 
> It's not a package, it's just me being sarcastic about Cygwin providing a port of the UN*X "mt" command; "EVAR" is a misspelling of, and capitalization of, "ever", in the style of mocking excessively-enthusiastic e-mail/Web forum/etc. messages.
> 
> I think at least once I've had my path set incorrectly when building Wireshark on Windows, and getting the wrong command run - a Cygwin port of some UN*X command being run instead of some other Windows tool that had the same name but was a different tool.  I think that's happened for me at least once with "mt" - and, if not me, with somebody else asking wireshark-dev about it.
> 
> That's why I wanted you to run "where mt.exe", to see whether it was picking up Cygwin's "mt".  From the output you got, it appears that it wasn't picking up Cygwin's "mt", so that's apparently not the cause of the problem.

I checked in a change in r38781 to make sure "mt" spins manifests
instead of motors.