On 4/15/2013 02:50, Hin-Tak Leung wrote:
--- On Sun, 14/4/13, Vincent Povirk madewokh...@gmail.com wrote:
Well, here's a simple thing you can
check: Does your zlib dll link to
_lseek or _lseeki64? The first one uses a 32-bit offset.
Wine's
implementation
--- On Mon, 15/4/13, Nikolay Sivov bungleh...@gmail.com wrote:
On 4/15/2013 02:50, Hin-Tak Leung
wrote:
--- On Sun, 14/4/13, Vincent Povirk madewokh...@gmail.com
wrote:
Well, here's a simple thing you can
check: Does your zlib dll link to
_lseek or _lseeki64? The first one uses a
I am porting an application which uses zlib's gzseek quite extensively to do
pseudo- random access of the content of large gz'ed files, in the same manner
of some's use of posix's lseek.
On small test data, it works correctly on wine. (identical result as linux). On
production data - a large
considering how old zlib is and the vast number of windows application which
uses zlib
Given how many people duplicate the effort to package zlib, the fact
that they're rarely updated, and the sort of problems gnulib exists to
work around, it would not surprise me if your particular zlib
--
On Sun, Apr 14, 2013 22:34 BST Vincent Povirk wrote:
considering how old zlib is and the vast number of windows application which
uses zlib
Given how many people duplicate the effort to package zlib, the fact
that they're rarely updated, and the sort of
Well, here's a simple thing you can check: Does your zlib dll link to
_lseek or _lseeki64? The first one uses a 32-bit offset. Wine's
implementation (http://source.winehq.org/source/dlls/msvcrt/file.c#L1090)
expands that to 64-bit and later truncates the file offset to 32-bit.
For a file larger
--- On Sun, 14/4/13, Vincent Povirk madewokh...@gmail.com wrote:
Well, here's a simple thing you can
check: Does your zlib dll link to
_lseek or _lseeki64? The first one uses a 32-bit offset.
Wine's
implementation (http://source.winehq.org/source/dlls/msvcrt/file.c#L1090)
expands that to
