X-Spam-Check-By:	sourceware.org
From:	ericblake AT comcast DOT net (Eric Blake)
To:	keinnamens AT excite DOT com, cygwin AT cygwin DOT com
Cc:	"keinnamens AT excite DOT com" <keinnamens AT excite DOT com>
Subject:	Re: procedure entry point getline could not be located
Date:	Sat, 14 Jan 2006 05:58:54 +0000
Message-Id:	<011420060558.16671.43C8931E0000B6720000411F22007613940A050E040D0C079D0A@comcast.net>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

> 
> What further steps can I take to try and fix the error "The procedure entry 
> point getline could not be located in the dynamic link library cygwin1.dll"?

Although you did extensive research, you failed to realize that providing
the output of "cygcheck -svr" is essential to helping us determine your
problem.  However, my guess is as follows:

You are probably running cygwin 1.5.18 and tried the experimental
findutils 4.2.27-1.  This won't work.  Findutils 4.2.27 is experimental
for a reason - it depends on getline(), which cygwin1.dll did not
provide until in the snapshots following 1.5.18.  To fix the problem,
either downgrade findutils back to the stable 4.2.25-2, or
upgrade cygwin to a current snapshot (see earlier threads from
this week for instructions on installing a snapshot).

--
Eric Blake
volunteer cygwin findutils maintainer

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