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
X-Injected-Via-Gmane:	http://gmane.org/
To:	cygwin AT cygwin DOT com
From:	Charles Wilson <cwilson AT ece DOT gatech DOT edu>
Subject:	Re: Today's version of pcre:
Date:	Thu, 05 Jun 2003 22:02:44 -0400
Lines:	37
Message-ID:	<3EDFF644.6000402@ece.gatech.edu>
References:	<5 DOT 2 DOT 1 DOT 1 DOT 2 DOT 20030605100122 DOT 00b301c8 AT ingber DOT securesites DOT com> <3EDF5007 DOT 1050601 AT cygwin DOT com> <3EDF512F DOT 7040001 AT burri DOT to>
Mime-Version:	1.0
X-Complaints-To:	usenet AT main DOT gmane DOT org
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
X-Accept-Language:	en-us, en
In-Reply-To:	<3EDF512F.7040001@burri.to>

Brian E. Gallew wrote:

> Larry Hall wrote:
> 
>> Lester Ingber wrote:
>>
>>> I can't start up my cygwin shell due to "cygpcre.dll not found", and 
>>> I cannot get the older 4.1 version under setup to install the older 
>>> 4.1 as recommended by Max?
> 
> 
> Easy answer:
> cd /usr/bin
> cp cygpcre-0.dll cygpcre.dll

Arrrgghhh! NO!  DON'T do that!  NEVER ever EVER suggest "renaming a DLL" 
as a fix.  There is ALWAYS a reason that the maintainer of a package 
(who undoubtedly knows more than you about the library in question -- 
otherwise you'd be the maintainer and not him) chose to change the name. 
  Don't undo what s/he, for very good reasons, did.

You would have had no way of knowing the specifics of the pcre upgrade 
issue at the time you posted your advice, because the "[ANNOUNCEMENT] 
New PCRE ..." message hadn't been posted yet.  But, the 'never suggest 
renaming a DLL' is, and will be, a good rule of thumb to follow 
regardless of package.

Concerning PCRE:

Anything that depended on the old cygpcre.dll can get it by installing 
the new 'libpcre' package.  Thanks to recent updates on the servers, 
setup should figure this out automatically.  But there was a time this 
morning when you could have inadventently broken your system.  Sorry for 
the trouble.

--Chuck



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