I think Goswin is suggesting to compile your code using large-file support. This will define off_t as a 64bit integer. Then you can use lseek on both 32bit and 64bit system with identical results (since off_t is 64bit on both platforms).
Building software with large-file support involves defining one or more constants depending on the OS. If you use autoconf to build your source tree, then you can use the AC_SYS_LARGEFILE macro to define the correct macros. One caveat I have found is when building on AIX, but that is probably irrelevant for this discussion... -Ted On Monday 14 March 2005 14:05, Taketoshi Sano wrote: > Hi. > > Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > > Just plain lseek will do. With _FILE_OFFSET_BITS=64 that is all you > > need. I don't see the point of using the lseek64 alias. > > I don't know much about that. My experience told me > that libc5 system had llseek, but glibc system don't. > And _llseek has just worked on both of them. > > If you know much about 64bit file access, then please > let me know, what point do you see of using > "just plain lseek and _FILE_OFFSET_BITS=64". > And, I want to know from which version of glibc > we can use it safely (or can we use it on libc5 too ?) > > It will help me to explain this to the upstream. > > Thanks. > -- > Taketoshi Sano: > <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
