Hi,
Having successfully built (and tested) a static openssl-1.0.0e library using
a mingw64 compiler (gcc-4.7.0) in the msys shell, make install croaks with:
##############################
making install in apps...
make[1]: Entering directory `/c/comp/openssl-1.0.0e/apps'
installing openssl
chmod: changing permissions of `C:/_64/msys/1.0/local_470/bin/openssl.new':
Bad file number
make[1]: *** [install] Error 1
make[1]: Leaving directory `/c/comp/openssl-1.0.0e/apps'
make: *** [install_sw] Error 1
##############################
When I look in the destination directory (C:/_64/msys/1.0/local_470/bin/) I
find that 'make install' has placed a file named 'openssl.new.exe' in there.
What's the correct fix for this ?
And what's the hack that will allow me to install the already-built
openssl-1.0.0e without rebuilding from scratch ?
The config command I ran was:
./config no-shared zlib
os/compiler:x86_64-w64-mingw32-gcc -I/usr/local_470/include -L/usr/local_470/lib
-lz -lws2_32 -lgdi32 -lcrypt32 --prefix=C:/_64/msys/1.0/local_470
After running that, in order for the build to succeed, I had to insert the
following into the beginning of the generated include/openssl/ocsp.h:
#if defined(OPENSSL_SYS_WINDOWS)
#include <windows.h>
#undef X509_NAME
#undef X509_EXTENSIONS
#undef X509_CERT_PAIR
#undef PKCS7_ISSUER_AND_SERIAL
#undef OCSP_REQUEST
#undef OCSP_RESPONSE
#endif
Not sure if the first line of that actually provides the portability that's
desired, but it works well enough for me.
After that, all goes well ... until 'make install', that is ;-)
Cheers,
Rob
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
