----- Original Message ----- From: "Brian Lewis" <br...@lorf.org>
> Have you built DLLs, though? Alas, no. Assuming you're gcc executable is named 'gcc.exe', you should be able to start with './config shared no_asm'. Then, in the resultant top level Makefile, remove the one occurrence of '-march=i486'. I think there will also be a need to remove the word 'static' from the definition of OPENSSL_IMPLEMENT_GLOBAL in e_os2.h. (That file is to be found in the top level folder and also in openssl/include - I amended both copies.) The changes that were made to store.h, pem.h and e_aep.c are probably still required, though the '-lws2_32 -lgdi_32' link should no longer be needed. But the problem I'm faced with is that 'no-asm' does not (afaict) actually provide 'no-asm' - because, if you look in the top level Makefile, you find: # CPUID module collects small commonly used assembler snippets CPUID_OBJ= uplink.o uplink-cof.o And, sure enough, very early into the 'make' process I get assembler errors: uplink-cof.s: Assembler messages: uplink-cof.s:5: Error: suffix or operands invalid for `push' uplink-cof.s:6: Error: suffix or operands invalid for `push' [snip] uplink-cof.s:173: Error: suffix or operands invalid for `push' uplink-cof.s:174: Error: suffix or operands invalid for `push' That's a show stopper for me. (That doesn't mean it can't be worked around - it just means that I don't know *how* to work around it. I'll ask about that on the openssl mailing list.) Cheers, Rob ------------------------------------------------------------------------------ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
