MIME-Version: 1.0
In-Reply-To: <54A098E33E92A04EB0DD9A2E8B546CB05F8F18B8@us-ex-mbx1.terastack.bluearc.com>
References: <54A098E33E92A04EB0DD9A2E8B546CB05F8F18B8@us-ex-mbx1.terastack.bluearc.com>
Date: Sun, 15 Nov 2009 20:47:36 +0000
Message-ID: <416096c60911151247x6e21c41cta62d640329c79c85@mail.gmail.com>
Subject: Re: cygwin_create_path import stops executable from running on 1.5  	since 1.7.0-63
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

2009/11/15 Martin Dorey:
> Linking a C program using 1.7.0-63 or 1.7.0-64 causes this runtime error =
when attempting to run the program on Cygwin 1.5:
>
> "The procedure entry point cygwin_create_path could not be located in the=
 dynamic link library cygwin1.dll".
>
> This happens with gcc-3 or gcc-4 - it's the Cygwin version that matters. =
=C2=A0I could reproduce this with a program as simple as:
>
> int main() {
> }
>
> http://www.cygwin.com/ml/cygwin/2009-11/msg00203.html leads me to think t=
hat the new import comes from Chuck's r1.2 pseudo-reloc.c changes for versi=
on 2 pseudo-relocs shortly before -63.

That's fine. Programs compiled on 1.7 aren't designed to be able to
run on 1.5. Before the reloc changes, you'd already get an error if
your program used ctype functions.

(1.5-compiled programs should of course run on 1.7.)

Andy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple