On Feb 9 14:37, Denis Excoffier wrote: > On Thu, Feb 09, 2012 at 12:06:31PM +0100, Corinna Vinschen wrote: > >> > So it's the same DLL path, just one time with the long pathname prefix > >> > (or better: The Win32 equivalent to the native NT path prefix). But, > >> > as I wrote in my mail to Heiko, neither the Windows loader nor the > >> > GetModuleFileName call normalize the path. So I think I just apply > >> > my patch to use only the basename in the dll_init code. > >> > >> I applied a patch and generated a new snapshot. Please give it a try. > > Usually after installation of a new snapshot i begin with a compilation > of the sources. Today the compilation fails in winsup/cygwin/mkimport > (perl script) with the following messages: > 1 [main] perl 2380 child_info_fork::abort: unable to map Glob.dll, > Win32 error 126 > 4 [main] perl 5460 child_info_fork::abort: unable to map Cwd.dll, Win32 > error 126 > 5 [main] perl 5916 child_info_fork::abort: unable to map Glob.dll, > Win32 error 126 > 4 [main] perl 4028 child_info_fork::abort: unable to map Cwd.dll, Win32 > error 126 > 4 [main] perl 4900 child_info_fork::abort: unable to map Glob.dll, > Win32 error 126 > 4 [main] perl 2128 child_info_fork::abort: unable to map Cwd.dll, Win32 > error 126 > 4 [main] perl 5120 child_info_fork::abort: unable to map Glob.dll, > Win32 error 126 > 4 [main] perl 5440 child_info_fork::abort: unable to map Cwd.dll, Win32 > error 126 > 4 [main] perl 5044 child_info_fork::abort: unable to map Glob.dll, > Win32 error 126 > 4 [main] perl 5456 child_info_fork::abort: unable to map Cwd.dll, Win32 > error 126 > etc. > > at the pace one message each 5seconds. > All processes indicated remain in /proc, as <defunct>, and with > maps "permission denied".
Sigh. While the basename is all we need to test if a DLL is already loaded, it's *not* enough to load a DLL which still needs loading, if the DLLs are not in the DLL search path, as in the case of Perl libs. I'm going to generate a new 2012-02-09 snapshot right now. Should be up in 10 minutes or so. Thanks for the report, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
