X-Spam-Check-By:	sourceware.org
Message-ID:	<458EE598.3010404@aim.com>
Date:	Sun, 24 Dec 2006 15:39:52 -0500
From:	Charli Li <KBarticle889459 AT aim DOT com>
User-Agent:	Thunderbird 3.0a1 (Windows/20061224)
MIME-Version:	1.0
To:	Cygwin Mailing List <cygwin AT cygwin DOT com>
CC:	Cygwin-Apps Mailing List <cygwin-apps AT cygwin DOT com>
Subject:	Updated cygwin dlls don't have the .dll extension; instead have .dll.new
X-AOL-IP:	70.20.177.184
X-Mailer:	Unknown (No Version)
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

When using setup.exe to update packages that includes dlls (such as
cygwin), it installs the dlls, but have a different file extension.
When I tried to start up bash after updating packages with new dlls,
bash briefly spits out an error saying that it couldn't find
cygreadine6.dll.  zsh and company started up normally, though.  I then
had to go to /bin (in Windows Explorer) and find out what was going on.
 Fishy enough, the new dlls had a filename extension of .dll.new
(example: cygreadline6.dll.new).  I then had to manually rename all the
new dlls that had the .dll.new extension.

Bottom line: Is this a problem with setup.exe?  CCing to cygwin-apps as
well.

--
Charli
---
Why are you still here, hippo?


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