On Sun, Mar 17, 2013 at 5:20 PM, Ed Beroset <beroset@xxxxxxxxxxxxxx> wrote:
>
>
>
> -----Original Message-----
>>From: Evan Huus <eapache@xxxxxxxxx>
>>Sent: Mar 17, 2013 12:09 PM
>>To: Developer support list for Wireshark <wireshark-dev@xxxxxxxxxxxxx>
>>Subject: Re: [Wireshark-dev] [Wireshark-commits] buildbot failure in Wireshark (development) on Windows-XP-x86
>>
>>I'm still not having any luck (and I've reread
>>https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html to
>>no avail). I have two shells available: cygwin's bash and windows'
>>cmd.exe.
>>
>>If I run cmd.exe and then run the vcvars32 script, I can build
>>Wireshark correctly using nmake. This seems to be working fine.
>>
>>I I run cygwin then I do not have nmake available. Running the
>>vcvars32 script from cygwin does not seem to change this (should it)?
>>
>>I cannot run test.sh from cmd.exe since cmd.exe will not interpret
>>unix shell scripts. I cannot run test.sh from cygwin since it requires
>>nmake, which I cannot get cygwin to recognize.
>
> Here's what I did (that worked). First, from a cmd.exe prompt, I set up the build environment as per https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html#ChSetupPrepareCommandCom (using the script there). Next, I ran \cygwin\bin\bash to get a bash shell. Then I fixed the path (under bash) using the command "export PATH=$PATH:/bin" and then I changed to the test directory "cd test". Finally, I ran the test script from there "./test.sh -c" and everything worked. If that works for you (or if it doesn't) let us know. Since I was the last person to edit that portion of the developer's guide, I'd like to know your thoughts on how it should be edited so that this will be easier to understand. It's definitely not intuitive, but I'm not sure where this test-specific information should be placed. Any ideas would be welcome.
That did the trick, thanks. I did initially try running bash from
inside cmd.exe but I got a ton of errors and it wasn't obvious that
the cause was my PATH variable.
One thing worth noting: during my initial setup I never looked at
vcvars32 or the batch script in the documentation, since my Visual
Studio installation created this handy "Visual Studio Command Prompt"
link which seems to do all that stuff for you (except for adding
C:\cygwin\bin to the PATH)!
As to where to put this information, I would just stick in a section
"2.2.14. Optional: Running the Test Suite" and put it there.
Anyways, it's now failing on test 4.2.3 (still not the one the
buildbot fails on!) with the message "tshark: Child dumpcap process
died: Access violation". Is that the win equivalent of a segfault?
Thanks,
Evan
