Wireshark-dev: Re: [Wireshark-dev] complie fail on WinXP 32bit
From: Andreas Heise <[email protected]>
Date: Tue, 24 Mar 2009 07:31:10 +0100
yes now I could also interpret the problem in the "verify_tools" output,
but before it was not clear for me as the tool found version of grep.
I was not clear that this was not enought...
C:\wireshark>nmake -f Makefile.nmake verify_tools

Microsoft (R) Program Maintenance Utility, Version 9.00.30729.01
Copyright (C) Microsoft Corporation.  All rights reserved.

Checking for required applications:
        cl: /cygdrive/c/Programme/Microsoft Visual Studio 9.0/VC/BIN/cl
        link: /cygdrive/c/Programme/Microsoft Visual Studio 9.0/VC/BIN/li
        nmake: /cygdrive/c/Programme/Microsoft Visual Studio 9.0/VC/BIN/n
        mt: /cygdrive/c/Programme/Microsoft SDKs/Windows/v6.0A/bin/mt
        bash: /usr/bin/bash
        bison: /usr/bin/bison
        flex: /usr/bin/flex
        env: /usr/bin/env
        grep: /cygdrive/c/Programme/Borland/BDS/4.0/Bin/grep
        /usr/bin/find: /usr/bin/find
        perl: /usr/bin/perl
        C:\Python26\python.exe: /cygdrive/c/Python26/python.exe
        sed: /usr/bin/sed
        unzip: /usr/bin/unzip
        wget: /usr/bin/wget


2009/3/23 Gerald Combs <[email protected]>
Stig Bjørlykke wrote:
> 2009/3/23 Andreas Heise <[email protected]>:
>> I found the problem, as you assumed it was a problem of other grep version
>> which was in the path of an old Borland Delphi installation.
> I can remember someone had this problem before.  Can we add a check for this?

"nmake -f makefile.nmake verify_tools" will show you the paths for each required
tool. Is this sufficient?

Join us for Sharkfest’09  |  Stanford University, June 15 – 18
Sent via:    Wireshark-dev mailing list <[email protected]>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:[email protected]?subject=unsubscribe