This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

NMAKE : fatal error U1073

0

I find this error while i am trying to execute

C:\Workplace\Development\wireshark-1.12.3>nmake -f Makefile.nmake all

Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved.

NMAKE : fatal error U1073: don't know how to make 'Wireshark-win32-libs-1.12\c-a res-1.9.1-1-win32ws\bin\libcares-2.dll' Stop.

asked 26 Feb '15, 03:37

Dhruv%20Gupta's gravatar image

Dhruv Gupta
6446
accept rate: 0%

What does nmake -f makefile.nmake verify_tools show?

(26 Feb '15, 03:52) grahamb ♦

C:\Workplace\Development\wireshark-1.12.3>nmake -f Makefile.nmake verify_tools

Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved.

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

    nmake: 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
    peflags: /usr/bin/peflags
    perl: /usr/bin/perl
    c:\Qt\4.8\vs2008\bin\qmake: /cygdrive/c/Qt/4.8/vs2008/bin/qmake
    sed: /usr/bin/sed
    unzip: /usr/bin/unzip
    wget: /usr/bin/wget

(27 Feb '15, 01:16) Dhruv Gupta

Have you run the setup target to download the required packages?

(27 Feb '15, 01:53) Anders ♦

Yes Sir..

nmake -f Makefile.nmake setup executed successfully..

(27 Feb '15, 02:25) Dhruv Gupta

C:\Workplace\Development\wireshark-1.12.3>nmake -f Makefile.nmake setup

Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved.

Checking for required applications: cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/bin/x86_amd64/cl link: /usr/bin/link nmake: 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 peflags: /usr/bin/peflags perl: /usr/bin/perl sed: /usr/bin/sed unzip: /usr/bin/unzip wget: /usr/bin/wget cd "C:\Wireshark-win32-libs-1.12" rm -r -f adns-1.0-win32-05ws rm -r -f c-ares-1.5.3ws rm -r -f c-ares-1.6.0ws rm -r -f c-ares-1.7.0-win??ws rm -r -f c-ares-1.7.1-win??ws rm -r -f c-ares-1.9.1-1-win??ws rm -r -f gettext-0.14.5 rm -r -f gettext-runtime-0.17 rm -r -f gettext-runtime-0.17-1 rm -r -f gettext-0.17-1 # win64 rm -r -f glib rm -r -f gnutls-2.8.1-1 rm -r -f gnutls-2.8.5--win??ws rm -r -f gnutls-2.10.3--win??ws rm -r -f gnutls-2.12.18--win??ws rm -r -f gnutls-3.1.22--win??ws rm -r -f gnutls-3.2.15-*-win??ws rm -r -f gtk2 rm -r -f gtk+ rm -r -f gtk-wimp rm -r -f kfw-2.5 rm -r -f kfw-3-2-2-final rm -r -f kfw-3.2.2-ws1 rm -r -f kfw-3-2-2-i386-ws-vc6 rm -r -f libiconv-1.9.1.bin.woe32 rm -r -f lua5.1 rm -r -f lua5.1.4 rm -r -f lua5.2.? rm -r -f libsmi-0.4.5 rm -r -f libsmi-0.4.8 rm -r -f libsmi-svn-40773-win??ws rm -r -f nasm-2.00 rm -r -f nasm-2.02 rm -r -f nasm-2.09.08 rm -r -f pcre-6.4 rm -r -f pcre-7.0 rm -r -f portaudio_v19 rm -r -f portaudio_v19_2 rm -r -f upx301w rm -r -f upx303w rm -r -f user-guide rm -r -f zlib123 rm -r -f zlib125 rm -r -f zlib-1.2.5 rm -r -f zlib123-dll rm -r -f AirPcap_Devpack_1_0_0_594 rm -r -f AirPcap_Devpack_4_0_0_1480 rm -r -f AirPcap_Devpack_4_1_0_1622 rm -r -f GeoIP-1.4.5ws rm -r -f GeoIP-1.4.6-win??ws rm -r -f GeoIP-1.4.8-win??ws

(27 Feb '15, 02:32) Dhruv Gupta

Downloaded all the packages

*** user-guide-g7ea0d6c.zip *** No HTTP proxy specified (http_proxy and HTTP_PROXY are empty). Downloading user-guide-g7ea0d6c.zip into '/cygdrive/c/Wireshark-win32-libs-1.12', installing into user-guide File 'user-guide-g7ea0d6c.zip' already there; not retrieving.

Extracting '/cygdrive/c/Wireshark-win32-libs-1.12/user-guide-g7ea0d6c.zip' into'/cygdrive/c/Wireshark-win32-libs-1.12/user-guide' Verifying that the DLLs and EXEs in user-guide are executable.

upx303w.zip No HTTP proxy specified (http_proxy and HTTP_PROXY are empty). Downloading upx303w.zip into '/cygdrive/c/Wireshark-win32-libs-1.12', installing into . File 'upx303w.zip' already there; not retrieving.

Extracting '/cygdrive/c/Wireshark-win32-libs-1.12/upx303w.zip' into '/cygdrive/c/Wireshark-win32-libs-1.12/.' Verifying that the DLLs and EXEs in . are executable.

nasm-2.09.08-win32.zip No HTTP proxy specified (http_proxy and HTTP_PROXY are empty). Downloading nasm-2.09.08-win32.zip into '/cygdrive/c/Wireshark-win32-libs-1.12', installing into . File 'nasm-2.09.08-win32.zip' already there; not retrieving.

Extracting '/cygdrive/c/Wireshark-win32-libs-1.12/nasm-2.09.08-win32.zip' into '/cygdrive/c/Wireshark-win32-libs-1.12/.' Verifying that the DLLs and EXEs in . are executable.

Wireshark is ready to build.

(27 Feb '15, 02:34) Dhruv Gupta
showing 5 of 6 show 1 more comments

One Answer:

0

OK, it appears to me that you're attempting to build Wireshark 1.12.3 64 bit using VS2008 and with QT. I'm not entirely sure this will work.

For 1.12.3 the recommended compiler is VS2010, the Express edition will build as well as regular editions, but VS2013 Community Edition is also free to install and works as well.

From your output, the first run of verify_tools looks odd, you have the 32 bit amd64 compiler listed and the 32 bit x86 linker and the nmake item should I think have the full path to nmake the same as cl and the linker:

cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/bin/x86_amd64/cl
link: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/BIN/link
nmake: nmake

The second run as part of setup has an incorrect linker (the Cygwin one):

cl: /cygdrive/c/Program Files/Microsoft Visual Studio 9.0/VC/bin/x86_amd64/cl
link: /usr/bin/link
nmake: nmake

So there's something odd in your environment. How did you setup the command prompt for building?

answered 27 Feb '15, 03:54

grahamb's gravatar image

grahamb ♦
19.8k330206
accept rate: 22%

its done.., thanks grahamb

(04 Mar '15, 19:38) Dhruv Gupta

It might help others if you describe what your actual issue was and how you fixed it.

If an answer has solved your issue, please accept the answer for the benefit of other users by clicking the checkmark icon next to the answer. Please read the FAQ for more information.

(05 Mar '15, 01:47) grahamb ♦