Wireshark · Wireshark-dev: Re: [Wireshark-dev] (Script)-Problem building current SVN-revision of Wireshark under WindowsXP

["Anders Broman \(AL/EAB\)" <anders.broman@xxxxxxxxxxxx>]

Hi,
As a workaround it's also possible to do dos2unix on the tools/win32-setup.sh file.
BR
Anders

________________________________

Från: wireshark-dev-bounces@xxxxxxxxxxxxx genom Jaap Keuter
Skickat: on 2006-11-22 17:14
Till: Developer support list for Wireshark
Ämne: Re: [Wireshark-dev] (Script)-Problem building current SVN-revision of Wireshark under WindowsXP



Hi,

Read back the message threads on Bash. There were/are issues with the
latest releases. A rollback to an older one resolved that.

Thanx,
Jaap

On Wed, 22 Nov 2006, Benjamin Meyer wrote:

> Hello
>
> I would like to build an uptodate version of Wireshark.
> I checked out SVN-Revision 19955 from
> http://anonsvn.wireshark.org/wireshark/trunk to a local directory.
>
> I test the installed tools with "nmake -f Makefile.nmake
> verify_tools" and get the following result:
>
> --- snip ---
>
> C:\WireShark>nmake -f Makefile.nmake verify_tools
>
> Microsoft (R) Program Maintenance Utility   Version 6.00.9782.0
> Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
>
>         bash tools\win32-setup.sh --appverify  cl  link  nmake  bash
>    bison
>  flex    env     grep    /usr/bin/find   perl    env python      sed
>    unzip
>  wget
> : command not foundh: line 2:
> : command not foundh: line 8:
> : command not foundh: line 11:
> 'ools/win32-setup.sh: line 12: syntax error near unexpected token `{
> 'ools/win32-setup.sh: line 12: `err_exit () {
> NMAKE : fatal error U1077: 'bash' : return code '0x2'
> Stop.
>
> --- snap ---
>
>
>
> The problem is:
> If I download "wireshark-0.99.4.tar" (via Download-page) and do
> "verify_tools" it works just fine and I can build Wireshark without
> any problem.
>
>
>
> --- snip ---
>
> C:\Kram\wireshark-0.99.4>nmake -f Makefile.nmake verify_tools
>
> Microsoft (R) Program Maintenance Utility   Version 6.00.9782.0
> Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
>
>         bash tools\win32-setup.sh --appverify  cl  link  nmake  bash
>    bison
>  flex    env     grep    /usr/bin/find   perl    env python      sed
>    unzip
>  wget
> Checking for required applications:
>         cl: /cygdrive/d/PROGRA~1/MICROS~3/VC98/BIN/cl
>         link: /cygdrive/d/PROGRA~1/MICROS~3/VC98/BIN/link
>         nmake: /cygdrive/d/PROGRA~1/MICROS~3/VC98/BIN/nmake
>         bash: /usr/bin/bash
>         bison: /usr/bin/bison
>         flex: /usr/bin/flex
>         env: /usr/bin/env
>         grep: /usr/bin/grep
>         /usr/bin/find: /usr/bin/find
>         perl: /usr/bin/perl
>         env: /usr/bin/env
>         python: /usr/bin/python
>         sed: /usr/bin/sed
>         unzip: /usr/bin/unzip
>         wget: /usr/bin/wget
>
> --- snap ---
>
> Any ideas what I can do? I am not familiar with this script-based
> building process.
> In cygwin the following script-versions are installed:
>
> This is perl, v5.8.7 built for cygwin-thread-multi-64int
>
> Python 2.4.3 (#1, May 18 2006, 07:40:45)
> [GCC 3.3.3 (cygwin special)] on cygwin
>
>
> Thank you for hints.
>
> Benjamin Meyer
> _______________________________________________
> Wireshark-dev mailing list
> Wireshark-dev@xxxxxxxxxxxxx
> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>
>

_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev

<<winmail.dat>>