Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-10-27 Thread Cook, Timothy
cludes "\" not "/", correct the slashes. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ulf Lamping > Sent: Thursday, October 26, 2006 4:34 PM > To: Developer support list for Wireshark > Subject: Re: [Wires

Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-10-27 Thread Neil Piercy
Hi, Ulf Lamping wrote: > Yes, the current cygwin python binding has some problems, I've installed > it and compile without your changes! I just don't really understand why??? No, I am totally confused as to what triggers the issue: I had a working build environment on one PC with Windows Python

Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-10-26 Thread Ulf Lamping
Neil Piercy wrote: > Any chance of getting this patch applied ? I've updated the patch in > bugzilla (#1157, not the typo'ed number below) to the latest SVN. > > Hi! Yes, the current cygwin python binding has some problems, I've installed it and compile without your changes! I just don't real

Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-10-26 Thread Neil Piercy
Any chance of getting this patch applied ? I've updated the patch in bugzilla (#1157, not the typo'ed number below) to the latest SVN. Neil Neil Piercy wrote: > I finally got round to raising bug #1175 and adding the proposed patch. > > Thanks, > Neil > > Joerg Mayer wrote: >> On Fri, Sep 08,

Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-10-11 Thread Neil Piercy
I finally got round to raising bug #1175 and adding the proposed patch. Thanks, Neil Joerg Mayer wrote: > On Fri, Sep 08, 2006 at 10:24:24AM +0100, Neil Piercy wrote: >> I submitted this a few days ago, but it hasn't made it to the SVN as far >> as I can see - is there a problem with it (I can b

Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-09-08 Thread Joerg Mayer
On Fri, Sep 08, 2006 at 10:24:24AM +0100, Neil Piercy wrote: > I submitted this a few days ago, but it hasn't made it to the SVN as far > as I can see - is there a problem with it (I can believe that ;-), or > did it just overflow the stack ? The preferred way to send patches is to send the to t

Re: [Wireshark-dev] Follow up to making register.c - python problem - patch

2006-09-08 Thread Neil Piercy
I submitted this a few days ago, but it hasn't made it to the SVN as far as I can see - is there a problem with it (I can believe that ;-), or did it just overflow the stack ? Neil Index: asn1/rrlp/Makefile.nmake === --- asn1/rrlp/

[Wireshark-dev] Follow up to making register.c - python problem - patch

2006-09-01 Thread Neil Piercy
This issue bubbled around in mid July, but I forgot to submit a patch - here is a patch which changes the native Windows PYTHON lines from using "/" to "\" as directory separators - I _think_ I've got all the makefiles... Neil Index: asn1/rrlp/Makefile.nmake