On Thu, May 04, 2006, Frank Bttner wrote: > No I only use mingw without MSYS because other lib's that I mus use can > not run with MSYS.(The Qt lib).
You should only have to build using MSYS, not run under it. Are the binaries produced by an MSYS build unusable with the other libs you use? The MSYS change was partly because its needed for FIPS. > In the INSTALL.W32 file of the package it call's > GNU C (MinGW) > ------------- > >ms\mingw32 > > but this have to Bug's the first is simple to fix with the line change. > But the second is harder, I have only a fix for it after the build error > occurs but not how to fix the perl scrip that generates the wrong make > file. > The fix was this: > perl x86cpuid.pl gaswin > x86cpuid.s > as -o x86cpuid.o x86cpuid.s > then I copied x86cpuid.o to the tmp folder (where the make file creates > all the *.o files) and added $(OBJ_D)\x86cpuid.o to the dependencies for > CRYPTOOBJ in the ms\mingw32a.mak makefile. > mingw32-make -f ms/mingw32a.mak > and then > dllwrap --dllname libeay32.dll --output-lib out/libeay32.a --def > ms/libeay32.def out/libcrypto.a -lwsock32 -lgdi32 > dllwrap --dllname libssl32.dll --output-lib out/libssl32.a --def > ms/ssleay32.def out/libssl.a out/libeay32.a > this works but it is not fine. And I have not fount yet the error in the > perl files. > That probably needs some hacking in the makefile generator for mingw. I had to manually add some dependencies for that kind of thing in VC++. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Funding needed! Details on homepage. Homepage: http://www.drh-consultancy.demon.co.uk ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
