Ciao guys,
hopefully I will finally have a bit of time for testing the new
3.2.0b code, especially after all the great work done by Lachlan.
I tried to run on my Debian Woody the configuration script, but I
encountered a 'small' problem with the zlib directory specification.
Usually, when I run configure with just the 'with-zlib' option
(without specifying any exact dir), I assume the default dirs are
scanned. On the other hand, I get a weird result: the configure script
goes searching for libraries in a 'yes/include' and 'yes/lib' directory
(which prevents the library to be linked by libtool).
Anyone over there had the same problem? If I specify --with-zlib=/usr
the installation goes on.
Ciao
-Gabriele
Il dom, 2003-05-25 alle 16:18, Lachlan Andrew ha scritto:
> Greetings all,
>
> The current check for zlib (which explicitly adds -I/usr/include or
> -I/usr/local/include if --with-zlib=... isn't specified) breaks the
> compile farm's Solaris setting. (/usr/include/stdargs.h is not gcc
> compatible.)
>
> Does anyone know
> (a) Why the default paths are added explicitly
> (b) Why AC_CHECK_LIB(z, inflateEnd) was run twice?
>
> Cheers,
> Lachlan
--
Gabriele Bartolini - Web Programmer
Comune di Prato - Prato - Tuscany - Italy
g.b...@co... | http://www.comune.prato.it
> find bin/laden -name osama -exec rm {} ;
|
