On 07/06/2011 06:59, sagar sg wrote:
ya, i have done all those steps.
On Tue, Jun 7, 2011 at 11:20 AM, Anders
Broman <a.broman@xxxxxxxxxxxx>
wrote:
Have you uncommented
the line
# "Microsoft Visual Studio 2005"
# Visual C++ 8.0, _MSC_VER 1400, msvcr80.dll
MSVC_VARIANT=MSVC2005
in Config.nmake?
The default is Visual C++ 9.0
Regards
Anders
sagar sg skrev 2011-06-07 07:26:
the errors i am getting are
Generating Code...
Compiling...
packet-ipmi-storage.c
packet-ipmi-transport.c
packet-ipmi-pps.c
packet-ipmi-update.c
packet-dcerpc-nt.c
Generating Code...
NMAKE : fatal error U1077: '"C:\Program
Files\Microsoft Visual Studio 8\VC\BIN\c
l.EXE"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program
Files\Microsoft Visual Studio 8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program
Files\Microsoft Visual Studio 8\VC\BIN\n
make.exe"' : return code '0x2'
Stop.
On Tue, Jun 7, 2011 at 10:04
AM, sagar sg <sagu072@xxxxxxxxx>
wrote:
the below is the
error iam getting.
"zlib1.dll.manifest : general error c1010070:
Failed to load and parse the manifest. The system
cannot find the file specified."
please help .
thanks and regards
Sagar.
On 06/06/2011 07:42, sagar sg
wrote:
hi,
while compiling source code of
wireshark i am getting error as
match686.obj file not found, i
have match686.asm file, i think
its not getting compiled during
the execution of makefile.nmake,
wha may be the problem please
help.
regards
Sagar
I successfully
compiled trunk on win32 just a
little while ago. Can you post the
last few lines of the compilation
output so we can see exactly what
has gone wrong. In
addition are you compiling from svn or
zip sources?
--
Regards,
Graham Bloice
I think
somethings not right in your build environment, I haven't built
with VC2005 for some time though.
Can you post the output of "set" from your build command prompt,
removing any personal or company information?
I know it's not in the developers guide, but personally with a
version as old as VC2005 I used to install the latest SDK and
set my build environment to use the tools from there as there
have been many bug fixes. The simplest way to do this (after
installing the SDK) is to navigate to the Start Menu entry for
the SDK and open the "CMD Shell". If the defaults aren't good
for you (e.g. on a 64 bit OS the default is set to x64
compilations, then simply copy the start menu entry and edit the
target tacking on "/x86". See the "SetEnv.cmd" file itself for
additional flags.
Having got a suitably prepared command shell, then cd to the
Wireshark directory and run the normal build procedure.
--
Regards,
Graham Bloice
|
