Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <3EDFF796.6040001@ece.gatech.edu> Date: Thu, 05 Jun 2003 22:08:22 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: cygwin AT cygwin DOT com Subject: Re: Today's revision of pcre : possible cause of damage? References: <000701c32b66$f1a225e0$6fc82486 AT medschool DOT dundee DOT ac DOT uk> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Ronald Landheer-Cieslak wrote: > This is my fault - sorry :( > > To fix this, run > $ cd /usr/bin > $ cp cygpcre-0.dll cygpcre.dll > $ cp cygpcreposix-0.dll cygpcreposix.dll > in your shell or > >>cd path\to\cygwin\bin >>copy cygpcre-0.dll cygpcre.dll >>copy cygpcreposix-0.dll cygpcreposix.dll > > in cmd/command.com BAD habit. While this solution does work in this particular case, it is a VERY bad idea to start encouraging the "rename DLL meme" as a general solution to DLL problems. It does NOT work in the general case, and can seriously muck up somebody's system if they don't know EXACTLY what they are doing. And usually, the only person who knows EXACTLY what they are doing when it comes to renaming DLLs, is the package maintainer. But in this case... Ronald, you already provided the right fix for this problem: the 'new' backward-compatibility package, 'libpcre'. Folks who experience a problem should install this new package -- and, as you pointed out, thanks to last-minute fixes to various setup.hint files, setup.exe should NOW take care of this automatically. --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/