On 2010-05-30 19:18, Ozkan Sezer wrote: > On Sun, May 30, 2010 at 12:29 PM, Wolfgang Glas <[email protected]> wrote: >> The only problem I encounterd was, that all DLLs linked with dllwrap produce >> an 'application failed to load properly (0xc0000412)' windows error. This was >> tha case for zlib, which I now link using gcc. However, for openssl-0.9.8n I >> don't have the possibility to switch to gcc linking, because openssl-0.9.8 >> traditionally used dllwrap. (I know, openssl-1.0.0 is out, but I have lots of >> software, which has not yet been reviewed for 1.0.0 compatibility, so be >> patient >> with me...) >> >> Does anbody know, whether dllwrap has recently been fixed in binutils CVS >> and >> whether the 20100527 snapshot eventually contains such a fix? > > AFAIK, dllwrap had no recent changes in the sourceware CVS. > I'd like to know if it behaves differently with the 2010-05-27 build > but I really doubt it would. It might be something with the recent
Ozkan, ThX for your reply. FYI, I've managed to link openssl-0.9.8n using gcc in the meanwhile, which works around the problem for me. Honestly, I doubt that dllwrap is of great value for producing new libraries. AFAIK, dllwrap has been used to wrap static libraries, which are given in binary form and do not properly declare dllimport/dllexport in their headers. However, the last usecase can nowadys be established by using gcc -Wl,--dll -shared libmyoldlib.a myoldlib.def -o myoldlib.dll -Wl,--import-lib, libmyoldlib.dll.a so I'm not sure whether we will find any usecase that can solely be established by dllwrap... Anywaxs, tha tool is there and some legacy Makefiles stick to using it, so it should be fixes in the mid term run. Best regards, Wolfgang ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
