Clifford Thrasher wrote:
Graham Bloice wrote:
Graeme Lunt wrote:
Hi,
Graham Bloice wrote:
I built a U3 version from SVN 20915, but the resulting .u3p fails to
install on my SanDisk MicroCruzer.
Does the package downloaded from:
http
like to point out that a list of compiler errors is not very
helpful without a context, i.e. the compiler line that preceded the errors.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org
the #ifdef _WIN32
block down to below the other includes fixes it as including winsock2.h
first will stop the winsock.h attempting to redefine things.
Another similar occurrence is in gui_utils.c. I've checked in fixes in
r21335.
--
Regards,
Graham Bloice
Ulf Lamping wrote:
Graham Bloice wrote:
CANDIA, Fabrice wrote:
The nmake used is C:\Program Files\Microsoft Platform SDK for Windows
Server 2003 R2\Bin and not the directory mentioned in the developper's
guide (Visual studio dir). Is it normal ?
The paths shown in the dev guide
better base to prevent new warnings from
leak into the sources.
Our mission continues ...
Thanks for rousing us into action. It had grated with me for a long
time, but I didn't have your resolve, nor Sebastian's commitment.
--
Regards,
Graham Bloice
easier.
I don't think it makes much difference. The loader will check for the
manifest in both places and the assemblies identified in the manifest
must be available.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
installation.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
,
but not for a long time.
Others have built it using VS2003, VS2005 and VS2005EE. I have no idea
what OS they used.
The tool depends.exe can be of use to find out what DLL's an exe expects
to use.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev
. Click OK.
After a suitable period of time you should have the source tree on your
local hard disk. Continue as per the developers guide.
--
Regards,
Graham Bloice
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev
Gisle Vanem wrote:
Graham Bloice [EMAIL PROTECTED] wrote:
Gisle Vanem wrote:
The #pragma warning() statements are MSVC specific. So
embed them inside #ifdef _MSC_VER.
I always thought unrecognised #pragma directives were ignored. I take
it that MinGw barfs on them in some way?
MingW
have VS 2005, so moving isn't an issue
for me, but should we consider dropping support for earlier VC versions.
This might clean up a few things.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
Ulf Lamping wrote:
Graham Bloice wrote:
On MSVC 6.0 + PDSK, I had to remove the Wx from CFLAGS to allow
compilation to proceed due to a warning emitted when compiling
packet-parlay.c.
The warning was that the number of lines exceed an internal limit
(65536) and no more line number info
local hard disk. Continue as per the developers guide.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Gisle Vanem wrote:
The #pragma warning() statements are MSVC specific. So
embed them inside #ifdef _MSC_VER.
I always thought unrecognised #pragma directives were ignored. I take
it that MinGw barfs on them in some way?
--
Regards,
Graham Bloice
Ulf Lamping wrote:
Graham Bloice wrote:
When compiling with MSVC 6.0 and the platform SDK, there are failures
due to the redefinition of sockaddr_storage in capture_wpcap_packet.c
and gtk/capture_if_details_dlg.c.
The definition is conditional on the version of MSVC used, whereas the
actual
defined, which is
indicated by the symbol _WINSOCK2API_. I think that using this symbol
would be preferable.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
to prefixing standard symbols with the letter g because
somebody decided to reinvent the wheel.
See comment above. The glib types help with a greater portability than
SUSv3.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
' to 'int ',
possible loss of data
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
.
--
Regards,
Graham Bloice
mpeg.c.diff.gz
Description: application/gzip
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
: unresolved
external symbol _mpa_versions
libwireshark.dll : fatal error LNK1120: 6 unresolved externals
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Graham Bloice wrote:
ronnie sahlberg wrote:
modified and checked in
2006-08-25 Shaun Jackman [EMAIL PROTECTED]
* asn1/Makefile.am (EXTRA_DIST): Add mpeg.
* asn1/mpeg/Makefile: New file.
* asn1/mpeg/mpeg-audio.asn: Ditto.
* asn1/mpeg/mpeg-audio.cnf: Ditto.
* asn1/mpeg/mpeg-pes.asn
?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Graeme Lunt wrote:
Hi,
Graham Bloice wrote:
I built a U3 version from SVN 20915, but the resulting .u3p fails to
install on my SanDisk MicroCruzer.
Does the package downloaded from:
http://prdownloads.sourceforge.net/wireshark/wireshark-0.99.5.u3p
install OK?
Yes it does, without
.
If the problem persists, contact the program software vendor.
The version of U3 Launchpad in use is 1.4.0.2
--
Regards,
Graham Bloice
Software Developer
Trihedral UK Limited
Tel: +44 (0)7002 874433
___
Wireshark-dev mailing list
Wireshark-dev
Graham Bloice wrote:
I built a U3 version from SVN 20915, but the resulting .u3p fails to
install on my SanDisk MicroCruzer.
When I run the U3 add programs applet, it reports:
U3 Launchpad failed to install U3 program, due to a possible error in
the program package. Try downloading
source?
Not that I know of. Why do you feel that you need to use a project?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Graham Bloice wrote:
I've been attempting to add tcp fragment reassembly using
tcp_dissect_pdus() to an existing dissector that already used the epan
reassembly code for an internal part of the protocol.
However it seems that when I add
I'm updating an older dissector (dnp3) and it uses a g_malloc() to build
a tmp buffer of data extracted in chunks from the tvb. A new tvb is
then created from this tmp buffer. After the new tvb (created by a call
to tvb_new_real_data()) is created the tmp buffer isn't used.
Which emem version
,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listinfo/wireshark-dev
Douglas Pratley wrote:
The wiki tips page has a couple of useful sections on debugging and
setting up browse info for MSVC.
http://wiki.wireshark.org/Development/Tips
You might also consider using WinDbg. It now has a GUI and once you get
the symbol and source paths sorted out
used to use a native python (I believed that it was faster), but
switched back to the default cygwin one time time ago with no problems
at all.
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http
makefile.nmake
verify_tools showed that Cygwin python was available on your system then.
From a bash shell what does env python produce?
--
Regards,
Graham Bloice
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman
and I'm not entirely sure what that
could be.
As a workaround, from within your bash shell navigate to epan/dissectors
and run the command:
python ncp.py -o packet-ncp.c
This should allow your build to proceed.
--
Regards,
Graham Bloice
A follow-up on issues when building wireshark on win32.
I found out that if Cygwin make package is installed, Wireshark cannot
be built anymore under win32 (cannot find cl and other dependencies).
It might be a conflict between Cygwin's make and nmake.
Does someone else have the issue? For
for Wireshark
Subject: Re: [Wireshark-dev] win32: nmake setup: can't find cl
Works fine for me, but then I don't have Cygwin on my normal
path. Do you?
No I don't have Cygwin in my path. Do you have Cygwin's make package
installed? In this case, it works for me too if I don't have the
901 - 935 of 935 matches
Mail list logo
