Dave Korn wrote: > Just to clarify: it is entirely standard for cygwin apps to use non-standard > cygXXX names for cygwin dlls to link against. It would be very nonstandard of > xmlcatalog to link against a dll with a standard libXXX name.
Right. And you should not find any package in the Cygwin distro that depends on a DLL named "libxml2.dll" because all Cygwin DLLs should begin with cyg. This leads me to believe that the poster has a foreign/non-cygwin version of xmlcatalog in his path which is actually being run from the postinstall. To the original poster: When you get the popup about the missing DLL, run something like Process Explorer and see exactly which xmlcatalog.exe is trying to be run. I'm willing to bet that it's not the Cygwin one and that you have a PATH problem, because the Cygwin xmlcatalog does not need any such libxml2.dll. 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/