On 29/08/2011 19:52, Ed Beroset wrote:
> Guy Harris wrote:
>> I think at least once I've had my path set incorrectly when building
>> Wireshark on Windows, and getting the wrong command run - a Cygwin port of
>> some UN*X command being run instead of some other Windows tool that had the
>> same
On 8/29/11 11:18 AM, Guy Harris wrote:
>
> On Aug 27, 2011, at 10:58 PM, Helge Kruse wrote:
>
>> What program package is EVAR, never heard about it.
>
> It's not a package, it's just me being sarcastic about Cygwin providing a
> port of the UN*X "mt" command; "EVAR" is a misspelling of, and cap
Guy Harris wrote:
>I think at least once I've had my path set incorrectly when building Wireshark
>on Windows, and getting the wrong command run - a Cygwin port of some UN*X
>command being run instead of some other Windows tool that had the same name
>but was a different tool. I think that's ha
On Aug 27, 2011, at 10:58 PM, Helge Kruse wrote:
> What program package is EVAR, never heard about it.
It's not a package, it's just me being sarcastic about Cygwin providing a port
of the UN*X "mt" command; "EVAR" is a misspelling of, and capitalization of,
"ever", in the style of mocking exc
On 28/08/2011 06:58, Helge Kruse wrote:
> Am 24.08.2011 11:32, schrieb Guy Harris:
>>
>> On Aug 24, 2011, at 1:52 AM, Graham Bloice wrote:
>>
>>> Is there any error message at all from the build after the call to mt.exe?
> No.
>
>>>
>>> From your command prompt after the build fails what is the ou
Am 22.08.2011 22:24, schrieb Andreas:
mt.exe -nologo -manifest "zlib1.dll.manifest"
-outputresource:zlib1.dll;2
The last command always crashes. The tool mt.exe loads zlib1.dll to
memory and doesn't find the correct run-time library.
This behavior is the same when I compile any other (not Wire
Am 24.08.2011 11:32, schrieb Guy Harris:
On Aug 24, 2011, at 1:52 AM, Graham Bloice wrote:
Is there any error message at all from the build after the call to mt.exe?
No.
From your command prompt after the build fails what is the output from "where
mt.exe"?
C:\Program Files\Microsoft SDKs
On Aug 24, 2011, at 1:52 AM, Graham Bloice wrote:
> Is there any error message at all from the build after the call to mt.exe?
>
> From your command prompt after the build fails what is the output from "where
> mt.exe"?
Because, after all, one of the most important bits of UN*X functionality EV
On 22/08/2011 21:24, Andreas wrote:
> Hello,
>
> I try to build Wireshark from source. Since you obviously built this program
> it must work, but theres one tool (mt.exe) that never works for me. I hope
> you can tell me what I'm doing wrong.
>
> 1. installed CYGWIN and Python 2.7
> 2. installed Mi
On 23/08/2011 21:55, Chris Maynard wrote:
> Andreas writes:
>
>> Am 23.08.2011 22:30, schrieb Chris Maynard:
>>> Andreas writes:
>>>
Yes, I tried. I need only libwireshark. That's why I reduced the make
targets to build. But, alas, I get exactly the same result, when I
"nmake all".
Am 23.08.2011 22:55, schrieb Chris Maynard:
Andreas writes:
Am 23.08.2011 22:30, schrieb Chris Maynard:
Andreas writes:
Yes, I tried. I need only libwireshark. That's why I reduced the make
targets to build. But, alas, I get exactly the same result, when I
"nmake all".
Can you verify th
Andreas writes:
> Am 23.08.2011 22:30, schrieb Chris Maynard:
> > Andreas writes:
> >
> >> Yes, I tried. I need only libwireshark. That's why I reduced the make
> >> targets to build. But, alas, I get exactly the same result, when I
> >> "nmake all".
> >
> > Can you verify that MSVC_VARIANT is s
Am 23.08.2011 22:30, schrieb Chris Maynard:
Andreas writes:
Yes, I tried. I need only libwireshark. That's why I reduced the make
targets to build. But, alas, I get exactly the same result, when I
"nmake all".
Can you verify that MSVC_VARIANT is set correctly in config.nmake?
MSVC_VARIANT=
Andreas writes:
> Yes, I tried. I need only libwireshark. That's why I reduced the make
> targets to build. But, alas, I get exactly the same result, when I
> "nmake all".
Can you verify that MSVC_VARIANT is set correctly in config.nmake?
Am 23.08.2011 00:42, schrieb Chris Maynard:
Andreas writes:
7. nmake -f Makefile.nmake config.h tools image codecs wsutil epan
Did you try "nmake -f Makefile.nmake all" as documented in the developer's
guide?
See: http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html#id505663
Andreas writes:
> 7. nmake -f Makefile.nmake config.h tools image codecs wsutil epan
Did you try "nmake -f Makefile.nmake all" as documented in the developer's
guide?
See: http://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html#id505663
_
Hello,
I try to build Wireshark from source. Since you obviously built this
program it must work, but theres one tool (mt.exe) that never works for
me. I hope you can tell me what I'm doing wrong.
1. installed CYGWIN and Python 2.7
2. installed Microsoft Visual Studio V9.0 (aka VS2008)
3. cal
17 matches
Mail list logo
