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
Message-ID: <4029067C.1E1154F5@dessent.net>
Date: Tue, 10 Feb 2004 08:27:40 -0800
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Problem rolling back cygwin from 1.5.7.1 to 1.5.5.1
References: <4028E5AB DOT 6030902 AT physics DOT ucla DOT edu> <20040210155340 DOT GB14638 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Christopher Faylor wrote:

> >       Since I've been having so much trouble with many different versions
> >       of emacs, I decided to try to go back to cygwin 1.5.5.1 using setup.exe.
> >It installs without any complaints and tells me to reboot before using.
> > So after rebooting, I keep getting an error message popping up when I
> >try to use bash or calling commands from perl:
> >
> >(title) Sh.exe: Entry Point Not Found
> >(body) The procedure entry point _fcntl64 could not be located in the
> >dynamically linked library cygwin1.dll.
> >
> >       Upgrading back to 1.5.7.1 solves this problem.  Has this been seen
> >before?  Is it possible to successfully downgrade cygwin back to
> >1.5.5.1? (Has anyone been having problems with emacs and 1.5.5.1?)
> 
> "I am having a hard time in France, so I have decided to move back to
> the US.  However, when I speak French to people in the US, I normally
> get a response of 'Huh?  I don't speak French.'
> 
> How do I solve this problem?"

To the original poster, in case you couldn't make any sense of that, the
english translation is: Current versions of Cygwin1.dll are
backwards-compatible but older versions of Cygwin1.dll are not
forwards-compatible, nor would it be possible for them to be.

Running older versions of the DLL is not supported, as you would have to
downgrade every other package on your system to a state that would
maintain binary compatibility.  It would be theoretically possible, of
course, but you'd have to work out which versions of the DLL each
package was compiled against and then hunt down enough previous versions
of all those packages to satisfy those dependencies.

Brian

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