Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: thing1-200.fsi.com: ford owned process doing -bs Date: Thu, 11 Mar 2004 17:23:02 -0600 (CST) From: Brian Ford X-X-Sender: ford AT thing1-200 Reply-To: cygwin AT cygwin DOT com To: Cygwin List cc: Kevin Stedman Subject: Re: _fnctl64 cannot be found In-Reply-To: <6.0.1.1.0.20040311163756.03a473b8@127.0.0.1> Message-ID: References: <20040311213139 DOT 15413 DOT qmail AT web60908 DOT mail DOT yahoo DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040311163756 DOT 03a473b8 AT 127 DOT 0 DOT 0 DOT 1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes 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/