Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-06 Thread Ed Beroset
Bill Meier wrote: >So: > >We should add 'cat' to the list of tools checked. I have been thinking about this. We could either do that or, perhaps somewhat perversely, we could use an alternative based on an already required application such as Perl or Python. Also, we don't necessarily care

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-06 Thread Weir, Alan
lighted my issue immediately. -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] 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-se

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-06 Thread Bill Meier
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

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-06 Thread Ed Beroset
Ed Beroset wrote: Weir, Alan wrote: Hi Ed, When running "nmake -f makefile.nmake verify_tools" the message: ERROR: The contents of C:\wireshark-win32-libs\current_tag.txt is (unknown). It should be 2011-06-27. Is emitted even though the file exists and contains the correct text. Ah, good cl

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-05 Thread Ed Beroset
Weir, Alan wrote: Hi Ed, When running "nmake -f makefile.nmake verify_tools" the message: ERROR: The contents of C:\wireshark-win32-libs\current_tag.txt is (unknown). It should be 2011-06-27. Is emitted even though the file exists and contains the correct text. Ah, good clue

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-05 Thread Weir, Alan
ed on both WIN XP SP2 and WIN2K8R2 Alan -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Ed Beroset Sent: Thursday, January 05, 2012 4:22 PM To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Problem wit

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-05 Thread Ed Beroset
"Weir, Alan" wrote: >The log indicates that the removal should be benign as it eliminated a warning >but in my case (and others based on googling the error message) it prevents >the cycwin path from being constructed correctly. > >I'm not a cycwin expert - anyone have any insight? Could be, but

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-05 Thread Weir, Alan
From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Chris Maynard Sent: Thursday, January 05, 2012 9:06 AM To: wireshark-dev@wireshark.org Subject: Re: [Wireshark-dev] Problem with tools/win-setup.sh Weir, Alan writes: > Suspecting a path issue I comp

Re: [Wireshark-dev] Problem with tools/win-setup.sh

2012-01-05 Thread Chris Maynard
Weir, Alan writes: > Suspecting a path issue I compared the win-setup.sh from the 1.4 and 1.7 > releases and found that the four lines of the form: > >   DEST_PATH=`cygpath --dos "$2"` > > Had been modified in 1.7 to remove the –dos flag. I > added this flag back in and re-ran the setup pha

[Wireshark-dev] Problem with tools/win-setup.sh

2012-01-05 Thread Weir, Alan
I had developed a plugin using version 1.4 and wanted to recompile against 1.7. I installed the sources, edited config.nmake to use VS2010 and executed "nmake -f Makefile.nmake verify_tools". I received the error message: C:\wireshark-win32-libs\current_tag.txt is (unknown) Creating this file j