[Zlib-devel] zlib 1.2.3.2 available for testing

Mark Adler madler at alumni.caltech.edu
Tue Sep 5 15:43:58 EDT 2006


On Sep 5, 2006, at 10:35 AM, Lasse Collin wrote:
> Defining z_off_t to be off64_t makes some applications to no longer
> compile, because off64_t isn't available on glibc unless
> _LARGEFILE64_SOURCE is defined.

In the 1.2.3.2, off64_t is used only when _LARGEFILE64_SOURCE is  
defined, and both are done only if the off64_t type is in sys/types.h  
when _LARGEFILE64_SOURCE is defined.

> I would prefer compiling zlib with _FILE_OFFSET_BITS=64 by default  
> (have
> a configure option to disable it), and using off_t instead of off64_t.

I used off64_t since I could test for it in configure and know for  
sure that the compiler option made sense and that the type is 64  
bits.  I'm not sure I like a solution where there is always a (long) - 
D compiler option that may or may not be relevant.

> Maybe all fseek()s should be converted to fseeko()/fseeko64() and
> ftell()s to ftello()/ftello64() when these functions are available.

Yes, I plan to add fseeko() detection to configure.

mark





More information about the Zlib-devel mailing list