Hi Graham, Thanks for the quick response. I re-ran the CMake in order to capture the log you described. Doing this it seemed to identify the correct cygwin path (to the 32 bit installation I installed after the 64 bit installation didn't appear to work). Running the build against these newly generated files succeeded.
Not sure if this indicates an issue with the 64 bit version of cygwin or some kind of mismatch between the two versions of cygwin installed on the machine... Thanks again for your help. Thanks Daniel On 11 November 2016 at 06:00, daniel mclean <maczor@xxxxxxxxx> wrote: > Hello, > > I've encountered some difficulties building Wireshark from source tthat I > was looking for some help with. I downloaded the Wireshark 2.2 source > tarball and followed the instructions from the step-by-step guide for a > Windows based x64 based build. The build gets quite a long way through but > I end up with the same error as: https://www.wireshark.org/ > lists/wireshark-dev/201602/msg00007.html > > 30> Building Custom Rule C:/Development-WS/wireshark/ > docbook/CMakeLists.txt > 30> CMake does not need to re-run because C:\Development-WS\wsbuild64\ > docbook\CMakeFiles\generate.stamp is up-to-date. > 30> Generating release-notes.txt > 30> 'LC_ALL' is not recognized as an internal or external command, > 30> operable program or batch file. > 30>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\ > v4.0\V120\Microsoft.CppCommon.targets(170,5): error MSB6006: "cmd.exe" > exited with code 9009. > > I have confirmed that both asciidoc and docxml are installed and have > tried a fresh cygwin environment and repeated the configuration steps. > > Can anyone else offer any other suggestions on what might be missing or > how I get some more information about what is relying on LC_ALL? > > Thanks > Daniel > > > I'm pretty sure I've seen this one before, is CMake running runa2x.sh using a non Cygwin bash? Please re-run your CMake generation step, redirecting the output to a file and then post the contents of that file. -- Graham Bloice
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
