While testing building Wireshark on Windows from a 'source tarball' (from
today) I encountered the following problems:
1. The airpdcap directory is accessed as part of the make (even if
AIRPCAP_DIR is not defined in config.nmake) but is not in the source tarball;
2. .../plugins/mate/moduleinfo.
Sebastien Tandel wrote:
> What is done hereabove when playing with subtrees is like acting as
> push/pop actions => then add this feature in the ptvcursor API. It can
> be done in the following way :
> - add a field in the ptvcursor structure which retains the push/pop of
> subtrees (fixed-length
Hi List!
Recently, there were repeating problems with the python implementation
shipped with cygwin.
Even after spending some annoying time in an attempt to fix this, there
wasn't a solution to this problem.
To fix this, I've changed the default settings in config.nmake to use
the native pyth
[EMAIL PROTECTED] wrote:
> Log:
> Uh Oh: Fix to properly set SH_FLAGS with 'igncr' if required as part of the
> nmake;
> I violated Murphy's nth law: thou shalt test fixes in an
> 'out of the box' configuration *not* in one's customized configuration.
> :(
>
Sounds like a "good trick (tm)"
Sebastien Tandel wrote:
>patch which changes input parameter type of a ctype function from
> (g)char to guchar avoiding undefined results.
Checked in.
___
Wireshark-dev mailing list
Wireshark-dev@wireshark.org
http://www.wireshark.org/mailman/listin
Stephen Fisher wrote:
> Is the temporary filename for capturing that starts with "ether" a relic
> from the Ethereal project name?
[I noticed this again today and remembered your post from a while back...]
Undoubtedly.
But the name of this temporary capture is everywhere: in the FAQ, the
Wik
Ulf Lamping wrote:
> Gerald Combs wrote:
>> The Windows builder has the native Python (2.4.4) installed. It's a
>> prerequisite for Buildbot.
>>
> Thanks for the info!
>
> Some remaining questions about the buildbot:
>
> Does the buildbot currently use the config.nmake from SVN (with cygwins
No. I was not able to.
This is the first time I'm trying to build out of source.
I installed the cygwin environment, and the develp env that are required.
The problem I see is that the dir. sturct. layout that comes from cygwin is
not what this package is expecting.
Under both cygwin or windows
Gerald Combs wrote:
> The Windows builder has the native Python (2.4.4) installed. It's a
> prerequisite for Buildbot.
>
Thanks for the info!
Some remaining questions about the buildbot:
Does the buildbot currently use the config.nmake from SVN (with cygwins
python) or does it use a customiz
Ulf Lamping wrote:
> I'll change the configuration accordingly soon. I'll guess the buildbot
> will fail from that moment until Gerald installs the Win32 python :-(
The Windows builder has the native Python (2.4.4) installed. It's a
prerequisite for Buildbot.
There was discussion on the list several months ago about an EtherCAT
plugin for wireshark. Has anyone done work on this?
I'd love to have a copy of the source as it stands right now, even if
it's not 100% ready for prime time.
Thanks,
Steve
___
Wir
Prokash Sinha wrote:
> I tried that too.
>
> What I was expecting is that if I follow the Developers doc, I should
> pretty much be able to build it, without much reconfigurations.
Unfortunately there were some fundamental changes in the cygwin tools
that are not updated in the Devel Guide.
>
Jaap Keuter wrote:
> Hi,
>
> Would it be a good idea to branch off into all kinds of native windows
> tools? I know cygwin can be a pain, but it puts all in one place, limiting
> version hell.
>
>
Yes, this is also my point of view.
But the first goal in this regard is to have a default config
Hi!
The current solution with the SH_FLAGS magic doesn't seem to work on my
machine - and the build problems of Prokash Sinha indicates that I'm not
alone with this.
I'm using the latest cygwin bash that provides the igncr option - but
the SH_FLAGS is empty when used in Makefile.nmake.
I've c
Hi,
Would it be a good idea to branch off into all kinds of native windows
tools? I know cygwin can be a pain, but it puts all in one place, limiting
version hell.
Just my $0.02
Jaap
On Tue, 26 Dec 2006, Ulf Lamping wrote:
> Hi List!
>
> The current default settings (config.nmake / Makefile.nma
Hi List!
The current default settings (config.nmake / Makefile.nmake) don't run
on my machine without changes - and I don't seem to be the only one (see
prokashs problems lately).
I'm wondering why the buildbot is running without problems - I guess
it's still using old cygwin tools.
These are
Hi,
At least I may try, but unfortunatly not before next year ;-(
Regards,
---
Frederic Roudaut
Selon Jaap Keuter <[EMAIL PROTECTED]>:
> Hi,
>
> Large patch, unfortunately it's mixed whitespace and code change.
> Could you split these out, making them easier to review?
>
> Thanx,
> Jaap
>
>
Hi all,
patch which changes input parameter type of a ctype function from
(g)char to guchar avoiding undefined results.
Regards,
Sebastien Tandel
Index: epan/dissectors/packet-sip.c
===
--- epan/dissectors/packet-sip.c(
Hi,
Checked in.
Thanx,
Jaap
On Tue, 26 Dec 2006, Sebastien Tandel wrote:
> Hi all,
>
>Here is a patch for the management of the bad/good checksum for ISIS
> (like TCP/UDP/IP).
> support added for :
> - booleans hf_isis_lsp_checksum_good, hf_isis_lsp_checksum_bad in the tree,
> - information
Hi,
Did you already build the setup target?
Thanx,
Jaap
On Mon, 25 Dec 2006, Prokash Sinha wrote:
> I tried that too.
>
> What I was expecting is that if I follow the Developers doc, I should pretty
> much be able to build it, without much reconfigurations.
>
> I installed the cygwin, and all r
20 matches
Mail list logo
