From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: The procedure entry point could not be located in cygwin1.dll
Date: Fri, 23 Sep 2016 22:35:00 -0000 [thread overview]
Message-ID: <253517ce-bfb4-499b-c5e9-25089f0a8a58@cornell.edu> (raw)
In-Reply-To: <CAF6RNtiDHaiSNW=n5oBEgwu1psj-=Mm_7-jtY7P1Zb1yNXukaA@mail.gmail.com>
On 9/23/2016 4:50 PM, William Forsyth wrote:
> I broke my win XP cygwin install such that bash fails to start.
>
> I used Setup.exe version 2.870.
>
> The install failed when trying to run the postinstall bash scripts.
>
> After the install failure bash fails every time with:
>
> The procedure entry point __locale_ctype_ptr could not be located in
> the dynamic link library cygwin1.dll.
>
>
> The install failed because it tried to install cygwin 2.6.0 which is
> not compatible with winxp.
>
>
> I reran Setup.exe to grab cygwin version 2.5.2-1 but the install still
> fails with the same cygwin1.dll error.
>
>
> Already tried to grab cygwin version 2.5.0 (which is the last known
> good cygwin version that ran on my machine) from the time machine, but
> I keep getting the same cygwin1.dll error. Any ideas how to fix this.
You probably have a version of bash that was built for cygwin-2.6.0.
Try reverting bash to whatever release was current just before
cygwin-2.6.0 was released.
Ken
--
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
next prev parent reply other threads:[~2016-09-23 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 21:08 William Forsyth
2016-09-23 22:35 ` Ken Brown [this message]
2016-09-23 23:00 ` William Forsyth
2016-09-23 23:12 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=253517ce-bfb4-499b-c5e9-25089f0a8a58@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).