X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Wed, 10 Sep 2008 18:11:04 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: setup.exe --quiet-mode Message-ID: <20080910221104.GA11152@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <48C0316C.F9E434A9@dessent.net> <00fc01c90f39$f4006970$9601a8c0@CAM.ARTIMI.COM> <007101c9136b$a62b3e10$9601a8c0@CAM.ARTIMI.COM> <48C841D0.ED2F523F@dessent.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48C841D0.ED2F523F@dessent.net> User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Wed, Sep 10, 2008 at 02:53:20PM -0700, Brian Dessent wrote: >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. Dave did suggest a possible workaround - delay any postinstall scripts until the next reboot. cgf -- 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/