From: wsgd
To: Developer support list for Wireshark
Sent: Thu, July 14, 2011 2:40:15 AM
Subject: Re: [Wireshark-dev] Wireshark v1.7.0 build issue with MSVC 2005
Le 13/07/2011 20:21, Pradip Biswas a écrit :
Hi,
>I tried building the latest 1.7.0
On Jun 26, 2011, at 3:32 PM, Michael Tüxen wrote:
> So you want to provide binaries for the libs and the include files and the
> other files needed? Where do you want to install them? System wide?
> We have to make sure that this does not conflict with the usage of some
> package managers running
On Jul 13, 2011, at 5:00 PM, Stephen Fisher wrote:
> The Windows-7-x64 buildbot is unhappy ("failed nmake docs") and hasn't
> dropped an automated build into
> http://www.wireshark.org/download/automated/win64 since the 7th.
>
> http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds
On 7/13/2011 7:38 PM, Guy Harris wrote:
Haven't you (and maybe others) been fixing the same issues already,
as a result of Coverity warnings about the same thing?
And how many of those are
static void
dissect_whatever(...)
{
...
proto_tree_add_item(tree, hf_foo, tvb,
Hello,
the attached patch fixes most of the remaining errors when compiling with
GTK_DISABLE_DEPRECATED. As I really don't have an idea whether that's the
way to go I decided to post it here instead of committing.
Btw. GtkItemFactory seems to be the core of most but no all remaining errors.
Ciao
The Windows-7-x64 buildbot is unhappy ("failed nmake docs") and hasn't
dropped an automated build into
http://www.wireshark.org/download/automated/win64 since the 7th.
http://buildbot.wireshark.org/trunk/builders/Windows-7-x64/builds/2360/steps/nmake%20docs/logs/stdio
Microsoft (R) Program Main
On Jul 13, 2011, at 7:23 AM, Bill Meier wrote:
> On 7/13/2011 8:05 AM, Jaap Keuter wrote:
>> Hi list,
>>
>> I think we need a new GCC option added to configure.in:
>>
>> AC_WIRESHARK_GCC_CFLAGS_CHECK(-Wno-unused-but-set-variable)
>>
>> This option came into existence with GCC 4.6 and is causin
Le 13/07/2011 20:21, Pradip Biswas a écrit :
Hi,
I tried building the latest 1.7.0 code on WinXP (32-bit) and Win7
(64-bit) both having MSVC 2005. I am stuck with the error "'ml': is
not recognized as an internal or external command, operable program or
batch file" almost at the beginning of "
On Wed, Jul 13, 2011 at 10:24:15PM +0200, Stig Bjørlykke wrote:
> Do we use deprecated functions?
Not that I'm aware of: the libgcrypt 1.5.0 release notes
(http://lists.gnupg.org/pipermail/gnupg-announce/2011q2/000307.html)
state that use of the Alternative Public Key Interface (gcry_ac_*)
fun
On Wed, Jul 13, 2011 at 8:13 PM, Stephen Fisher
wrote:
> Since we compile with -Werror, a workaround to fix Wireshark compilation
> is to add "#define _GCRYPT_IN_LIBGCRYPT 1 " before every include of
> gcrypt.h to convince the macros in gcrypt.h that it's being compiled
> with libgcrypt and that "
Hi Bill,
That option sounds good to me.
Thanks,
Jaap
Send from my iPhone
On 13 jul. 2011, at 16:47, Bill Meier wrote:
>> Re:
>>
>> > AC_WIRESHARK_GCC_CFLAGS_CHECK(-Wno-unused-but-set-variable)
>>
>> Is there a (reasionably easy) way to use this option only when compiling
>> in the .../diss
Hi,
I tried building the latest 1.7.0 code on WinXP (32-bit) and Win7 (64-bit) both
having MSVC 2005. I am stuck with the error "'ml': is not recognized as an
internal or external command, operable program or batch file" almost at the
beginning of "nmake -f Makefile.nmake all."
Do I need to do
On Wed, Jul 13, 2011 at 12:03:06PM -0600, Stephen Fisher wrote:
> This is happening simply by including gcrypt.h, so I e-mailed the
> gcrypt-devel mailing list and am awaiting a response:
Since we compile with -Werror, a workaround to fix Wireshark compilation
is to add "#define _GCRYPT_IN_LIBG
On Tue, Jul 12, 2011 at 10:07:09AM -0600, Stephen Fisher wrote:
> I probably upgraded libgcrypt as a local package recently and now when
> compiling Wireshark from trunk, it fails with:
>
> cc1: warnings being treated as errors
> In file included from packet-ssl-utils.h:37,
> fr
Re:
> AC_WIRESHARK_GCC_CFLAGS_CHECK(-Wno-unused-but-set-variable)
Is there a (reasionably easy) way to use this option only when compiling
in the .../dissectors directory ?
(I think that I've previously addressed the "unused_but_set" warnings
for many (all ?) of the other directories). (SVN 37
On 7/13/2011 8:05 AM, Jaap Keuter wrote:
Hi list,
I think we need a new GCC option added to configure.in:
AC_WIRESHARK_GCC_CFLAGS_CHECK(-Wno-unused-but-set-variable)
This option came into existence with GCC 4.6 and is causing havoc all over.
I've been going through a lot of dissectors, many of
I would be extremely careful with pcap_compile. Last time I checked the
sources. pcap_compile was not thread safe (because internally it uses global
variables), so you would need to use synchronization to protect concurrent
calls to that function.
Have a nice day
GV
-Original Message-
sagar sg writes:
> Hi, I have written a dissector plug in in windows and it works fine, now i
want to compile it in linux to get the .so file
Try reading doc/README.plugins.
___
Sent via:Wireshark-dev mailing list
If you followed the steps for plugin, you should see it.
.la will be in your dissector folder under plugin folder. .so is in .libs
inside of your dissector folder.
>Okay. i fallowed the steps u have mentioned , edited the makefiles as u
>mentioned and compiled the wireshark but i am not able to s
Hi list,
I think we need a new GCC option added to configure.in:
AC_WIRESHARK_GCC_CFLAGS_CHECK(-Wno-unused-but-set-variable)
This option came into existence with GCC 4.6 and is causing havoc all
over.
I've been going through a lot of dissectors, many of which have either:
* unused set variab
cant we compile the dissector shared library independently and link with
wireshark ?
On Mon, Jul 11, 2011 at 4:16 PM, Ankith Agarwal wrote:
>
> On Mon, Jul 11, 2011, sagar sg said:
>
> > Hi,
> > I have written a dissector plug in in windows and it works fine, now
> i
> > want to compile it
I've been using Gmail and thought you might like to try it out. Here's an
invitation to create an account.
You're Invited to Gmail!
sagar sg has invited you to open a Gmail account.
Gmail is Google's free email service, built on the idea that email can be
intuitive, efficient, and fun. Gmail
Okay. i fallowed the steps u have mentioned , edited the makefiles as u
mentioned and compiled the wireshark but i am not able to see any files
getting generated ( .la or .so ) ? how a typical makefile for wireshark
dissector code look like?
Thanks and Regards
Sagar
On Wed, Jul 13, 2011 at 3:01
Hi
Probably you should go through the Interlink plugin as done in the
wireshark code. You can Just take the Makefiles from there and make the
corresponding changes for your plugin...
so file is the share object file
la file is libtool library file
both files are auto generated after compil
I dont hvae .la file, when actually it gets generated.? and how?
On Mon, Jul 11, 2011 at 4:16 PM, Ankith Agarwal wrote:
>
> On Mon, Jul 11, 2011, sagar sg said:
>
> > Hi,
> > I have written a dissector plug in in windows and it works fine, now
> i
> > want to compile it in linux to get the
25 matches
Mail list logo
