X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 10 Sep 2008 18:11:04 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: setup.exe --quiet-mode
Message-ID: <20080910221104.GA11152@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <loom DOT 20080904T183156-413 AT post DOT gmane DOT org> <48C0316C DOT F9E434A9 AT dessent DOT net> <00fc01c90f39$f4006970$9601a8c0 AT CAM DOT ARTIMI DOT COM> <loom DOT 20080910T172329-77 AT post DOT gmane DOT org> <007101c9136b$a62b3e10$9601a8c0 AT CAM DOT ARTIMI DOT COM> <48C841D0 DOT ED2F523F AT dessent DOT 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 AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

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/