Re: [openssl-users] Failed to install OpenSSL 1.1.0 using 'nmake install'
Sorry, my mistake, those were the instructions I used for building openssl-1.0.2 When I do, for openssl-1.1.0: > perl Configure VC-WIN32 That works, and then I do: > nmake I get: Fatal error C1051: program database file, 'C:\...\openssl-1.1.0\ossl_static.pdb' has an obsolete format, delete it and recompile Andrew Hartley Senior Software Engineer Tel: +44 (0)1784 410 369 | Direct: +44 (0)1784 410 103 Email: andrew.hart...@taxcomputersystems.com Web: www.taxcomputersystems.com Tax Computer Systems Limited, Centurion House, London Road, Staines, TW18 4AX -Original Message- From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Richard Levitte Sent: 21 September 2016 14:10 To: openssl-users@openssl.org Subject: Re: [openssl-users] Failed to install OpenSSL 1.1.0 using 'nmake install' Andrew, I think you need to read up in the INSTALL file in 1.1.0. Jing Liu's sequence of commands seems correct to me, and with 1.1.0, the default install prefix *is* C:\Program Files (x86)\OpenSSL\ for VC-Win32. Cheers, Richard In message <c208566ee5ac44caad482acc09d09...@mailsvr.tcsl.taxcomputersystems.com> on Wed, 21 Sep 2016 12:54:58 +0000, Andrew Hartley <andrew.hart...@taxcomputersystems.com> said: andrew.hartley> Your step (4) to me appears to be wrong. If you are to install openssl andrew.hartley> to the following directory: andrew.hartley> andrew.hartley> C:\Program Files (x86)\OpenSSL\ andrew.hartley> andrew.hartley> then you need to do: andrew.hartley> andrew.hartley> Ø perl Configure VC-WIN32 –prefix=C:\Program Files (x86)\OpenSSL andrew.hartley> andrew.hartley> When I build openSSL I use nasm, so after the above I do: andrew.hartley> andrew.hartley> Ø ms\do_nasm andrew.hartley> andrew.hartley> Ø nmake –a –f ms\nt.mak andrew.hartley> andrew.hartley> Ø nmake –f ms\nt.mak test andrew.hartley> andrew.hartley> Ø nmake –f ms\nt.mak install andrew.hartley> andrew.hartley> Does that help at all? andrew.hartley> andrew.hartley> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On andrew.hartley> Behalf Of Jing Liu andrew.hartley> Sent: 21 September 2016 13:35 andrew.hartley> To: openssl-users@openssl.org andrew.hartley> Subject: [openssl-users] Failed to install OpenSSL 1.1.0 using 'nmake andrew.hartley> install' andrew.hartley> andrew.hartley> I’ve tried all my best to solve this problem but failed. Can you help andrew.hartley> me? andrew.hartley> andrew.hartley> - OS: Windows 10 andrew.hartley> andrew.hartley> - Perl: ActivePerl 5.12.2 build 1202 andrew.hartley> andrew.hartley> - Development environment: MS Visual Studio 2010 SP1 andrew.hartley> andrew.hartley> - OpenSSL version: OpenSSL 1.1.0 andrew.hartley> andrew.hartley> I tried to compile and install OpenSSL 1.1.0 according to the andrew.hartley> following steps: andrew.hartley> andrew.hartley> 1. decompressed OpenSSL 1.1.0 software package to directory andrew.hartley> "D:\openssl-1.1.0"; andrew.hartley> andrew.hartley> 2. opened the "Visual Studio 2010 command prompt" window using an andrew.hartley> Administrator identity; andrew.hartley> andrew.hartley> 3. switched to the directory "D:\openssl-1.1.0"; andrew.hartley> andrew.hartley> 4. D:\openssl-1.1.0> perl Configure VC-WIN32; andrew.hartley> andrew.hartley> 5. D:\openssl-1.1.0> nmake; andrew.hartley> andrew.hartley> 6. D:\openssl-1.1.0> nmake test; andrew.hartley> andrew.hartley> > So far, all steps went smoothly, but ... andrew.hartley> andrew.hartley> 7. D:\openssl-1.1.0> nmake install; andrew.hartley> andrew.hartley> Here, I got the following error and there was no file being copied to andrew.hartley> the destination directories even though those directories were andrew.hartley> successfully created. andrew.hartley> andrew.hartley> Microsoft (R) program maintenance utility 10.00.30319.01 copy right andrew.hartley> (C) Microsoft Corporation.All rights reserved. andrew.hartley> andrew.hartley> *** Installing development files andrew.hartley> andrew.hartley> created directory 'C:/Program Files (x86)/OpenSSL' andrew.hartley> andrew.hartley> created directory 'C:/Program Files (x86)/OpenSSL/include' andrew.hartley> andrew.hartley> created directory 'C:/Program Files (x86)/OpenSSL/include/openssl' andrew.hartley> andrew.hartley> Can't Open "./ms/applink.c" at .\util\copy.pl line 61. andrew.hartley> andrew.hartley> NMAKE : fatal error U1077: “C:\Perl\bin\perl.exe”: return code “0x16” andrew.hartley> andrew.hartley> Stop. andrew.hartley> andrew.hartley> __ andrew.hartley> Registered in England with company number 5347048 andrew.har
Re: [openssl-users] Failed to install OpenSSL 1.1.0 using 'nmake install'
Your step (4) to me appears to be wrong. If you are to install openssl to the following directory: C:\Program Files (x86)\OpenSSL\ then you need to do: ? perl Configure VC-WIN32 -prefix=C:\Program Files (x86)\OpenSSL When I build openSSL I use nasm, so after the above I do: ? ms\do_nasm ? nmake -a -f ms\nt.mak ? nmake -f ms\nt.mak test ? nmake -f ms\nt.mak install Does that help at all? From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Jing Liu Sent: 21 September 2016 13:35 To: openssl-users@openssl.org Subject: [openssl-users] Failed to install OpenSSL 1.1.0 using 'nmake install' I've tried all my best to solve this problem but failed. Can you help me? - OS: Windows 10 - Perl: ActivePerl 5.12.2 build 1202 - Development environment: MS Visual Studio 2010 SP1 - OpenSSL version: OpenSSL 1.1.0 I tried to compile and install OpenSSL 1.1.0 according to the following steps: 1. decompressed OpenSSL 1.1.0 software package to directory "D:\openssl-1.1.0"; 2. opened the "Visual Studio 2010 command prompt" window using an Administrator identity; 3. switched to the directory "D:\openssl-1.1.0"; 4. D:\openssl-1.1.0> perl Configure VC-WIN32; 5. D:\openssl-1.1.0> nmake; 6. D:\openssl-1.1.0> nmake test; > So far, all steps went smoothly, but ... 7. D:\openssl-1.1.0> nmake install; Here, I got the following error and there was no file being copied to the destination directories even though those directories were successfully created. Microsoft (R) program maintenance utility 10.00.30319.01 copy right (C) Microsoft Corporation.All rights reserved. *** Installing development files created directory 'C:/Program Files (x86)/OpenSSL' created directory 'C:/Program Files (x86)/OpenSSL/include' created directory 'C:/Program Files (x86)/OpenSSL/include/openssl' Can't Open "./ms/applink.c" at .\util\copy.pl line 61. NMAKE : fatal error U1077: "C:\Perl\bin\perl.exe": return code "0x16" Stop. __ Registered in England with company number 5347048 Registered office at Centurion House, London Road, Staines-upon-Thames, TW18 4AX This electronic message contains information from Tax Computer Systems Ltd (a wholly owned subsidiary of tax systems plc) which is confidential and may be privileged. The information is intended to be for the sole use of the individual(s) or entity to whom it is addressed. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify the sender by telephone or e-mail (to the number or e-mail address above) immediately and destroy the message and all attached documents. Reasonable care has been taken to ensure that this communication (and any attachments or hyperlinks contained within it) is free from computer viruses. No responsibility is accepted by taxsystemsplc and the recipient should carry out any appropriate virus checks. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] openssl-1.1.0 - Linker error on Windows
-Original Message- From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Michael Wojcik Sent: 25 May 2016 15:35 To: openssl-users@openssl.org Subject: Re: [openssl-users] openssl-1.1.0 - Linker error on Windows > From: openssl-users [mailto:openssl-users-boun...@openssl.org] On > Behalf Of Matt Caswell > Sent: Wednesday, May 25, 2016 08:05 > To: openssl-users@openssl.org > Subject: Re: [openssl-users] openssl-1.1.0 - Linker error on Windows > > > On 25/05/16 14:59, Michael Wojcik wrote: > > > >> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On > >> Behalf Of Andrew Hartley Sent: Wednesday, May 25, 2016 05:20 > > > >> I've built the openssl-1.1.0 library with no-shared config option > >> on Windows. I've linked the library to my application > and fixed > >> the few issues with EVP_MD_CTX deprication. When I build my > >> application I get the following link errors: > > > >> 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external > >> symbol __imp__CertFreeCertificateContext@4 referenced in function > >> _capi_free_key > > > > You have the CAPI engine linked into libcrypto (rather than > > configuring it for dynamic loading) > > IIRC it is no longer possible to build for static linking but > dynamically load engines (there be dragons). Perhaps not. I have a hybrid engine mechanism where I build OpenSSL as a static library but as sharable code, link it statically into my own shared library (DLL on Windows, shared object on Linux/UNIX), and add an engine at runtime. The engine is implemented in my library, so it's not actually dynamically loaded, but it isn't statically linked into OpenSSL either. That seems to work fine, at least for 1.0.1 and 1.0.2. (Of course, Configure doesn't actually support building OpenSSL as static libraries of sharable code, so we have to edit the configurations we use with each release. But such is life.) > >, so you need to link against the > > Windows CAPI library, which is crypt32.lib. Add /Lcrypt32, either > >when you create libcrypto or when you link your application. > > Another possibility, if you are not using the CAPI engine, is to > disable it during the OpenSSL build using the no-capieng Configure option. Yes. I was assuming Andrew wanted CAPI support and had configured it explicitly, but that isn't a safe assumption. If he doesn't need it, then disabling it in the configure options is the most sensible course. I've switched it off via the configure options. All working fine now thank you. Andrew __ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] openssl-1.1.0 - Linker error on Windows
I've built the openssl-1.1.0 library with no-shared config option on Windows. I've linked the library to my application and fixed the few issues with EVP_MD_CTX deprication. When I build my application I get the following link errors: 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertFreeCertificateContext@4 referenced in function _capi_free_key 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertGetCertificateContextProperty@16 referenced in function _capi_get_prov_info 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertOpenStore@20 referenced in function _capi_open_store 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertFindCertificateInStore@24 referenced in function _capi_find_cert 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertEnumCertificatesInStore@8 referenced in function _capi_find_cert 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertCloseStore@8 referenced in function _capi_find_key 1>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp__CertDuplicateCertificateContext@4 referenced in function _capi_load_ssl_client_cert Any advice on how this is to be fixed? Andrew __ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] openssl-1.1.0 - static linkage
I have now worked out what to do. I did a clean with: ? nmake clean and then successfully build the library with the no-shared config option. Andrew From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Andrew Hartley Sent: 25 May 2016 11:21 To: openssl-users@openssl.org Subject: [openssl-users] openssl-1.1.0 - static linkage I have previously used openssl-1.0.2 and was using it with static linkage into my program on Windows. I built it statically using the nt.mak file. I have now downloaded the source for openssl-1.1.0 and wish to build it statically. If I use the defaults, all builds fine with nmake and then installs into my path as setup with the prefix configure option. If I then configure with no-shared to generate a static library, I gets loads of "error LNK2019 : unresolved external symbol" errors. Would someone please advise me on how to successfully build openssl-1.1.0 statically. Many thanks Andrew __ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk __ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] openssl-1.1.0 - static linkage
I have previously used openssl-1.0.2 and was using it with static linkage into my program on Windows. I built it statically using the nt.mak file. I have now downloaded the source for openssl-1.1.0 and wish to build it statically. If I use the defaults, all builds fine with nmake and then installs into my path as setup with the prefix configure option. If I then configure with no-shared to generate a static library, I gets loads of "error LNK2019 : unresolved external symbol" errors. Would someone please advise me on how to successfully build openssl-1.1.0 statically. Many thanks Andrew __ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
