FW: cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63
Martin Dorey
http://software.jessies.org/downloads/windows/terminator-6.56.3178.msi should work around your problem, Al. Thanks for the report.
-----Original Message-----
From: cygwin...@cygwin.com [mailto:cygwin...@cygwin.com] On Behalf Of Martin Dorey
Sent: Sunday, November 15, 2009 12:15
To: cyg...@cygwin.com
Subject: cygwin_create_path import stops executable from running on 1.5 since
1.7.0-63
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. I 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 that the new import comes from Chuck's r1.2 pseudo-reloc.c changes for version 2 pseudo-relocs shortly before -63.
--
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Al Hagopian
Back in production!
Bless you mate.
Martin Dorey
(Dropping Al to bcc.)
> Subject: cygwin_create_path import stops executable from running on 1.5 since 1.7.0-63
That got a won't-fix, which I think is fair enough, though imo worthy of a release note and, as at least one of their developers tacitly agreed, worthy of having the error messages immortalized in their archives.
This leaves me in a quandary. One choice is to remove 1.7's exim and cron, so I can install and configure 1.5's, in order to build our production images with 1.5 once again. Another is to freeze my installation at 1.7.0-62 until such time as we feel like we can require 1.7, leaving it inconvenient for me to try to reproduce eg the cygpath issue that recently cropped up (and which I should have tried to reproduce, by upgrading, before blaming it on x64 Windows 7). They've just about missed their second self-imposed deadline for releasing 1.7.
Martin Dorey
I have successfully done battle with cron and exim, so back to 1.5 it is, with the .msi files that are up now.