On Thu, 11 Mar 2004, Larry Hall wrote: > At 04:31 PM 3/11/2004, you wrote: > >I just upgraded from 1.5.5 cygwin to 1.5.7 cygwin. > >When I try to run it I get _fnctl64 can not be found > >errors. > > > >The reason I upgraded was because I was trying to > >compile code that was using the >2GB calls like > >lseek64, fstat64, open64, ... > > You do know that this is automatic, right? You don't actually call lseek64, etc. lseek is translated to lseek64 at link time.
> >What am I missing in my cygwin build, because of these > >errors? > > > > You can't have upgraded from anything more than Cygwin 1.3.22 > if you're getting this complaint when you run. > Not true, his story does make sense. > 64 bit file operations were introduced for 1.5.1. > But, _fcntl64 didn't exist, and lseek didn't return the upper 32 bits because of a newlib prototype issue, until 1.5.6. I agree with the reboot or search for a duplicate cygwin1.dll part, though (assuming he's not trying to link directly to *64 syscalls). HTH -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
