This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.

Index Nav: Message Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] [Date Prev] [Date Next] [Thread Prev] [Thread Next] [Raw text]

# Re: Today's revision of pcre : possible cause of damage?

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

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/

Index Nav: Message Nav: [Date Index] [Subject Index] [Author Index] [Thread Index] [Date Prev] [Date Next] [Thread Prev] [Thread Next]