On Mon, Aug 24, 2009 at 10:33:39AM +0100, Colin Watson wrote: > So my reading of this is that, if zlib is following the same scheme (and > wouldn't anything else just be confusing?), then gzopen64 should only be > defined if _LARGEFILE64_SOURCE is defined, and otherwise gzopen should > just be straight 64-bit and gzopen64 should not be defined. Compare e.g. > <stdio.h>.
The problem is that with _FILE_OFFSET_BITS set to 64 zlib transparently maps the vanilla calls to their 64 bit equivalents so that everything is fine at link time but it does not prototype the 64 bit variants. > Perhaps this is really a bug in the callers? Not if they're using the regular calls - if they're trying to call the 64 bit variants directly I'd agree that they're at best suboptimal but they may be doing so as a result of rewriting within zlib. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
