In my case I had a collection of "tools" that I had acquired over the years (some as far back as the MKS toolkit!!) that were in my path and so were hiding the recently installed Cygwin versions - so yes, checking the required tools reside in the expected location would have highlighted my issue immediately.
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Bill Meier
Sent: Friday, January 06, 2012 8:12 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Problem with tools/win-setup.sh
On 1/6/2012 5:59 AM, Ed Beroset wrote:
> Ed Beroset wrote:
>> Then you've found your problem. Either rename the other cat or fiddle
>> with the path to point to the cygwin version of cat first. If that
>> doesn't do it, let us know and we'll dig a little deeper.
>
So:
We should add 'cat' to the list of tools checked.
It also sounds like:
We should require certain tools (bash, bison,...,sed,,...)
(in addition to the already checked /usr/bin/find) should
be in /usr/bin.
Does this seem too restrictive ?
ISTR previous cases where something other with the same
name as a cygwin exec (e.g. sed) was found because of the
way PATH was set up.
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe