Németh Márton wrote:
> I don't know much about the changes, do you know any idea what could went
> wrong?
>
> Márton Németh
>
> P.S.: Here is a copy of the "svn log" between the two revisions:
>
>
>
> r22635 | rich
Hi,
which platform and compiler do you use?
Based on gcc usage it seems you use any non-Windows platform as gcc is
not supported for Wireshark build on Windows.
But from __attribute__((dllexport)) it seems you use Windows platform.
Tomas
> -Original Message-
> From: [EMAIL PROTECTED]
Hi,
I found a regression: under Linux the raw USB packets can be caputred
until revision 22635, but cannot be starting with revision 22642. Between
these two revisions the revisions cannot be compiled from out of the box.
The bug report is here: http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2
Hello,
I am not actually new to Wireshark, i have build the plugin in
Wireshark which has to be decoded on the top of UDP. I m using this on
Window XP SP1 . I have build Wireshark with GTK+ 2.10.12 and Wireshark
Version is 0.99.6.
The problem with me is *Wireshark Crash* when the
On Thu, Dec 13, 2007 at 06:02:23PM +0530, Mayank Jain wrote:
> Making all in dissectors
> /usr/local/bin/python -o packet-ncp.c
> Unknown option: -o
> usage: /usr/local/bin/python [option] ... [-c cmd | -m mod | file | -]
> [arg] ...
> Try `python -h' for more information.
> *** Error code 2
It appears I found the problem. I ran verify_tools on my good install and it
showed sed as pointing to "c:\ent\appl\prod\bin", but I thought it was using
c:\cygwin\sed. The sed.exe in the \ent\...\bin dir on my dev machine was
outdated, so I copied the newer version and everything seems to be
I subscribed to this mailing-list after the discussion with above
subject seems to have ended. Problem is that on the archive-site
the email-adress of Graeme Lunt who asked for traces for Px-
communications. Can he/you contact me. I think I can provide some
traces but need to discuss some things in
I apologize, the -3 was a typo. I had to manually type the console output
since I am trying to build wireshark on a remote machine. I added the quotes
too, and still nothing.
If I run the command by itself from the command line, it appears to be OK. (No
output, but no errors).
___
Hi,
I am currently trying to build wireshark using VC++ 2005 EE on Windows
XP. I was able to do it on my own machine, but I had to move it over to
an offline machine to do some development. I cannot run nmake setup
since the system is offline, so I just copied the win32-lib folder from
own su
Hi,
The problem you have comes from the command line which calls the sed
unix command. The option "-3" does not exist for sed. You may replace
-3 by -e. I would also add double quote character (") after the first
-e option, like this :
sed -e "s/@VERSION@/0.3.1/" -e "s/@HAVE_LIBZ@/#define HAVE_
From: Diaconou, Alex
Sent: Thursday, December 13, 2007 10:33 AM
To: 'wireshark-dev@wireshark.org'
Subject: Trouble building wireshark: unrecognized command
Hi,
I am currently trying to build wireshark using VC++ 2005 EE on Windows
XP. I was able to
Just subscribed to this list. Following my old post.
Bug 2101 has been added to the database.
Thanks!
Jingshao
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Hi all,
I am getting following error during make command can anyone of you
please give your inputs regarding this error
Steps used during the building of wireshark
Checked out the code from this command
svn co http://anonsvn.wireshark.org/wireshark/trunk/ wireshark
./autogen.sh
Configure co
13 matches
Mail list logo
