search for: _fseek64_wrap

...in the files that get built on my FreeBSD system. That would be lib/vorbisfile.c. This includes a wrapper for seek_func which uses fseek() but alludes to the use of a 64-bit safe function where appropriate. I would say the same thing needs to be done for tell_func. Now, I need to ask about this _fseek64_wrap. Is it intended that this select the appropriate one of fseek64/fseeko/fseek/ whatever, based on what the OS supports? I'm assuming that it is, but that it isn't complete yet. Under this assumption, let me ask, how do you plan to select between the available 64-bit-safe functions for the...

...eally a good idea? For example, this compiles fine (on VC++ 6), but itsn't right: int ov_open(FILE *f,OggVorbis_File *vf,const char *initial,long ibytes){ ov_callbacks callbacks = { (size_t (*)(void *, size_t, size_t, void *)) fread, (int (*)(void *, ogg_int64_t, int)) _fseek64_wrap, (int (*)(void *)) fclose, (long (*)(void *)) ftell }; return ov_open_callbacks((void *)f, vf, initial, ibytes, callbacks); } int ov_open_callbacks(void *f,OggVorbis_File *vf,char *initial,long ibytes, ov_callbacks callbacks)...

Ivo, Your patch number 16347 uses _fseeki64 when _WIN32 is defined. Unfortunately, MinGW (or at least the Linux -> Win32 cross compiler I'm using) defines _WIN32 but isn't aware of _fseeki64. I have therefore modified your solution a little and commited it as rev 15376. The code now looks like this: #ifdef __MINGW32__ return fseeko64(f,off,whence); #elif defined

Greetings one and all; I'm not subscribed to this list so I'm first sending this message to verify that mails from me make it through, and then later I'll send the juicy messages with patches. Also, the address I'm using is IPv6-only and doesn't often work, so drop me from any replies and I'll catch the archives, or drop only the hostname part to get an IPv4 address that