Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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:	slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date:	Thu, 11 Mar 2004 16:59:33 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: _fnctl64 cannot be found
In-Reply-To:	<Pine.GSO.4.56.0403111642181.13117@slinky.cs.nyu.edu>
Message-ID:	<Pine.GSO.4.56.0403111657160.13117@slinky.cs.nyu.edu>
References:	<20040311213139 DOT 15413 DOT qmail AT web60908 DOT mail DOT yahoo DOT com> <Pine DOT GSO DOT 4 DOT 56 DOT 0403111642181 DOT 13117 AT slinky DOT cs DOT nyu DOT edu>
MIME-Version:	1.0
X-Scanned-By:	MIMEDefang 2.39

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, ...
> >
> >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.  64 bit file
> operations were introduced for 1.5.1.  You apparently have an
> old DLL hanging around somewhere.  Find it.  Delete it.  If
> you cannot find it, you may just need to reboot (because
> you didn't after setup asked you to).  If that's not it,
> throw out your computer and buy a new one.  It's apparently
> broken (i.e. there's no other reason for this kind of problem).
> --
> Larry Hall

On Thu, 11 Mar 2004, Igor Pechtchanski wrote:

> Kevin,
>
> Most likely your cygwin1.dll wasn't replaced by the upgrade because it was
> in use by one or more Cygwin processes.  The latest part of setup log
> (/var/log/setup.log) should contain "reboot replacement" if that is the
> case.  Simply reboot.  It's also possible (but very unlikely) that you
> have more than one version of cygwin1.dll on your system.
>
> For the future, it would have been easier if you had attached the output
> of "cygcheck -svr" to your bug report, as requested in the Cygwin problem
> reporting guidelines at <http://cygwin.com/problems.html>.
>         Igor

LOL.  Larry, we have got to stop doing this[*].  You take the even days,
and I'll take the odd ones, ok? ;-)
	Igor
[*] The above replies are essentially the same, and posted withing a
minute of each other.  And this isn't the first time, either.
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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/

- Raw text -