ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] win 64 wireshark build

From: Brian Oleksa <oleksab@xxxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 23 Jul 2009 14:39:11 -0400

Now I cannot get it to even build using 32 bit.

Verify tools works and setup also works...but when I do a nmake all....
This is the error that I get:

lemon.c
lemon.c : fatal error C1902: Program database manager mismatch; please check you
r installation
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN
\cl.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '..\native-nmake.CMD' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN
\nmake.exe"' : return code '0x2'
Stop.

Thanks,
Brian



Anders Broman wrote:
Hi,
What happens if you run nmake -f Makefile.nmake setup ?
I take it you'll need the win64 libraries any way.
Regards
Anders

-----Ursprungligt meddelande-----
Fr�n: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] F�r Brian Oleksa
Skickat: den 23 juli 2009 20:05
Till: Developer support list for Wireshark
�mne: Re: [Wireshark-dev] win 64 wireshark build

This is interesting.

If I change the config.nmake file back to: WIRESHARK_TARGET_PLATFORM=win32

and do a verify tools....everything works great..(see output below).

Why is this...?? I need the platform to say win64 to build a 64 bit version of this ...correct...??

Thanks,
Brian

C:\wireshark_july_09_64bit>nmake -f Makefile.nmake verify_tools

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


ERROR: The contents of C:\wireshark-win32-libs\current_tag.txt is 2008-11-15.
ERROR: It should be 2009-06-10-1.0.

Checking for required applications:
        cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/cl
link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link

nmake: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/nmake
        mt: /cygdrive/c/Program Files/Microsoft SDKs/Windows/v7.0/bin/mt
        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
        C:\Python26\python.exe: /cygdrive/c/Python26/python.exe
        sed: /usr/bin/sed
        unzip: /usr/bin/unzip
        wget: /usr/bin/wget


Graham Bloice wrote:
Brian Oleksa wrote:
Ok..here is the "set lib" output

C:\Program Files\Microsoft Visual Studio 9.0\VC>set lib
LIB=C:\Program Files\Microsoft Visual Studio 9.0\VC\ATLMFC\LIB;C:\Program Files\ Microsoft Visual Studio 9.0\VC\LIB;C:\Program Files\Microsoft SDKs\Windows\v7.0\
lib;
LIBPATH=Framework32\;Framework32\v2.0.50727;C:\Program Files\Microsoft Visual St
udio 9.0\VC\ATLMFC\LIB;C:\Program Files\Microsoft Visual Studio
9.0\VC\LIB;
Thanks,
Brian

Which shows that you are are not set up correctly for linking with the x64 MS libs. Instead of calling vcvars32.bat to set your build environment you need to use the 64 bit version. In my installation of VS2005 Pro, I have ...\VC\bin\vcvars32.bat, but I also have ...\VC\bin\amd64\vcvarsamd64.bat and ..\VC\bin\x86_amd64\vcvarsx86_amd64.bat. I would try one of the amd64 versions, don't know they're they're different.

--
Regards,

Graham Bloice
------------------------------------------------------------------------


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev

mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe