> I used this as a jumping point to investigate and can share some > information about the build on Win98 with mingw. I am also attaching a > patch for you to look at.
Please verify http://cvs.openssl.org/chngview?cn=20153. > It turns out that despite the logs I submitted > to you, unicows wasn't being used. A "strings openssl.exe" revealed no > "unicows" string in the executable. When I instead added "-lunicows" > to the beginning of the $lflags variable for mingw's config-string in > Configure, "unicows.dll" began to appear in the executable file. I am not > sure why this is. Neither am I... Why would implied change of linking order make such difference? But on the other hand why should it appear at all in either case? It should only appear if there is a reference to a UNICODE function from one of the real object modules. "Real" is used here to distinguish actual binary code from import stubs commonly found in e.g. libkernel32.a. And there shouldn't be any... In VC-WIN32 build we link with unicows.lib only if we compile with *optional* -DUNICODE, so it shouldn't be required in mingw build either... A. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
