X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <48C841D0.ED2F523F@dessent.net> Date: Wed, 10 Sep 2008 14:53:20 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: setup.exe --quiet-mode References: <48C0316C DOT F9E434A9 AT dessent DOT net> <00fc01c90f39$f4006970$9601a8c0 AT CAM DOT ARTIMI DOT COM> <007101c9136b$a62b3e10$9601a8c0 AT CAM DOT ARTIMI DOT COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Dave Korn wrote: > Err, that should never happen, unless you're updating from a > several-years-old DLL. The Cygwin DLL is intended to be backwardly > compatible, and only rarely have their been ABI breaks. So this aspect of > updating doesn't get tested very often. No, that's wrong. It is expected to see errors about missing entry points, because what's happening is a binary that was built against a newer cygwin DLL is being run against an older cygwin DLL because it could not be replaced. The backwards compatibility only works in the other direction, where you run an older binary against a newer DLL. There is no workaround for this. You either make sure the DLL isn't in use or you suffer from broken postinstalls (which usually means a broken installation.) There's really nothing else that can be done. Brian -- 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/