Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!howland.reston.ans.net!agate!violet.berkeley.edu!jkh From: jkh@violet.berkeley.edu (Jordan K. Hubbard) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: 2.0.5R: vim-3.0 anyone? Date: 16 Jul 1995 19:37:19 GMT Organization: University of California, Berkeley Lines: 15 Message-ID: <3ubppf$t98@agate.berkeley.edu> References: <95Jul14.213710.5319@ne.snafu.de> <3u7d8p$bdi@agate.berkeley.edu> <3u882m$afk@bell.maths.tcd.ie> <3ubhlh$d27@oz.plymouth.edu> NNTP-Posting-Host: violet.berkeley.edu In article <3ubhlh$d27@oz.plymouth.edu>, Ted Wisniewski <ted@oz.plymouth.edu> wrote: >Here is "mylseek", it returns a "long" instead of "off_t"; I cooerce the >type back to "off_t" in the calling procedure. I hope this helps in trouble >shooting the problem, I have heard that the problem persists in 2.0.5. Yikes! The `offset' parameter and return type of lseek are of type off_t for a reason; lseek works with 64 bit (long long) values now! You need to in order to deal with larger files.. Any code being recompiled for FreeBSD 2.0 and later should use off_t. There is a 32 bit compatability system call (olseek) for older binaries, but that's really not something you should call directly from source. Jordan