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: <004b01c32b69$17035280$78d96f83@pomello> From: "Max Bowsher" To: , References: <000701c32b66$f1a225e0$6fc82486 AT medschool DOT dundee DOT ac DOT uk> Subject: Re: Today's revision of pcre : possible cause of damage? Date: Thu, 5 Jun 2003 14:48:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Cam-ScannerAdmin: mail-scanner-support AT ucs DOT cam DOT ac DOT uk X-Cam-AntiVirus: Not scanned X-Cam-SpamDetails: fergus AT bonhard DOT uklinux DOT net wrote: > Sometime in the last couple of hours I ran setup.exe and upgraded pcre and > associated bits and pieces. Maybe I did something wrong but now there are > real rather than virtual files as follows: > > \usr\bin\cygpcre-0.dll > \usr\bin\cygpcreposix-0.dll > \usr\bin\pcregrep.exe > \usr\bin\pcretest.exe > > Also a call to less causes a "missing cygpcre.dll" error message. > > There may be other problems induced by this revision OR I really have > suffered a moderately damaging slipped finger whilst running it. Can anybody > confirm or otherwise? Thank you. Problem already noted, and the setup.hint files have been fixed. See cygwin-apps archive for details. It will take a little while for the next upset run to pick up the changes, and then for the new setup.ini to propagate to the mirrors. For a temporary workaround, revert the pcre package to the previous 4.1 version. Max. -- 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/