Douglas Pratley wrote:
> Hi Ulf
>
> 20614 builds for me. I haven't had a chance to look at it in any more
> detail yet. If I get time I will try to test some of the invalid
> configurations to see if the logic actually catches the invalid cases!
> (I assume you can confirm that it works for the 200
o: Developer support list for Wireshark
> Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 20609:
> /trunk//trunk/:config.h.win32
>
> Douglas Pratley wrote:
> > The logic of this looks wrong to me in one sense - the
> message tells
> > you that your compiler is 14.00
Douglas Pratley wrote:
> The logic of this looks wrong to me in one sense - the message tells you
> that your compiler is 14.00 when it is not (I'm still using 12.00). I
> would have thought it should be reversed, so that given a compiler
> number, it checks that the variant is one of the accepted
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ulf Lamping
Sent: 29 January 2007 22:23
To: wireshark-dev@wireshark.org
Subject: Re: [Wireshark-dev] [Wireshark-commits] rev 20609: /trunk/
/trunk/:config.h.win32
[EMAIL PROTECTED] wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.c
[EMAIL PROTECTED] wrote:
> http://anonsvn.wireshark.org/viewvc/viewvc.cgi?view=rev&revision=20609
>
> User: etxrab
> Date: 2007/01/29 08:58 PM
>
> Log:
> Comment out Ulfs changes to be able to do a test build.
>
>
Could you please explain that a bit further ?!?
If there's a bug in the logic, i
