This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: setup.exe --quiet-mode


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]