Fabrizio Bertocci wrote:
> Jeff Morriss wrote:
>> For the releases we (try to) turn off warnings as errors because, well,
>> we can't clean up all the warnings on all the platform+Glib/GTK+compiler
>> combinations--especially with compiler bugs.
>>
>> For 0.99.6 warnings-as-errors was turned off in
Jeff Morriss wrote:
>
> For the releases we (try to) turn off warnings as errors because, well,
> we can't clean up all the warnings on all the platform+Glib/GTK+compiler
> combinations--especially with compiler bugs.
>
> For 0.99.6 warnings-as-errors was turned off in the top level configure
> but
Fabrizio Bertocci wrote:
> Guy Harris wrote:
>>
>> That's not a bug, that's a feature; in 0.99.6, the default is to enable
>> warnings as errors, and you have to...
>>
>>
>>> If I run 'configure' with '--disable-warnings-as-errors' I don't get
>>> that compilation error, so it must be something
Guy Harris wrote:
That's not a bug, that's a feature; in 0.99.6, the default is to enable
warnings as errors, and you have to...
If I run 'configure' with '--disable-warnings-as-errors' I don't get
that compilation error, so it must be something in the configure script
that doesn't work qui
Fabrizio Bertocci wrote:
> I verified that the problem of zlib occur only on:
> - Redhat 9
> - Redhat Enterprise Linux 3
> In both platform the gzwrite is declared as:
> ZEXTERN int ZEXPORTgzwrite OF((gzFile file, const voidp buf,
> unsigned len));
That *should* define the second argumen
Guy,
About the problem with the location of the man pages.
I think the problem here is related to the autoconf version of whoever
generated the 'configure' script for the distribution.
I don't run autoconf when I build wireshark, instead I just launch the
./configure script.
In my opinion the pr
Guy,
I verified that the problem of zlib occur only on:
- Redhat 9
- Redhat Enterprise Linux 3
In both platform the gzwrite is declared as:
ZEXTERN int ZEXPORTgzwrite OF((gzFile file, const voidp buf,
unsigned len));
It appears that this problem has been fixed in newer version of libz
(
Fabrizio Bertocci wrote:
> [2] The RPM build still fail because apparently the man pages are now
> installed under $PREFIX/share/man instead of $PREFIX/man.
> The workaround is, again, to change the SPEC file (same as above),
> replacing the line:
> %prefix/man/*/*
> into:
> %prefix/share/man/*/
Fabrizio Bertocci wrote:
> [1] When building a rpm package, the rpm build fails because of a
> warning that is treated as error (when it should not be!).
> The problem is reported in: wiretap/file_access.c (line 993) (the
> warning is about passing a 'const' pointer to gzwrite that is declared
On Tue, Jul 31, 2007 at 10:42:30AM +0200, Radek Vok??l wrote:
> Fabrizio Bertocci wrote:
> > [3] On RedHat Enterprise 3, CentOS 3, and RedHat 9 the build fails
> > because the file:
> > gtk/export-object.c
> > uses some functions that are available only on GTK 2.4 and above.
> >
> > The correct fi
Fabrizio Bertocci wrote:
> [3] On RedHat Enterprise 3, CentOS 3, and RedHat 9 the build fails
> because the file:
> gtk/export-object.c
> uses some functions that are available only on GTK 2.4 and above.
>
> The correct fix is to #ifdef those sections to use the new API (GTK
> 2.4>) only if gtk+2.
All,
I tried to build wireshark 0.99.6 on several platforms and I discovered
several problems I'm reporting on this email.
I haven't been following up the mailing list, so I don't know if they
are known problems or not. Anyway:
[1] When building a rpm package, the rpm build fails because of a
12 matches
Mail list logo
