RE: Compilation error using OpenSSL 1.1.1i
> From: openssl-users On Behalf Of
> Jayalakshmi bhat
> Sent: Wednesday, 30 June, 2021 08:29
> I am getting the below error. Does anyone have inputs. Any help would be
> appreciated.
> openssl/safestack.h(159) : error C2054: expected '(' to follow '__inline__'
[I don't think I've seen a reply to this. If it's already been answered, my
apologies for the noise.]
With OpenSSL build questions, please always supply the Configure command line.
Offhand, it looks like your compiler doesn't recognize __inline__ as a
decoration on a function declaration, and the pp-token "ossl_inline" is defined
to expand to "__inline__".
Without digging through the configuration mechanism I can't say exactly how
ossl_inline is defined, but presumably it's set by configuration based on what
C implementation it believes you're using. So you may be using the wrong
Configure target, or that target may assume a different C compiler, or a newer
version of it.
--
Michael Wojcik
Re: compilation error
thx allot for quick reply i have modified the library name to ssl but i have the same problem with the linker error is Building file: ../src/certificate.cpp Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/certificate.d -MTsrc/certificate.d -o src/certificate.o ../src/certificate.cpp Finished building: ../src/certificate.cpp Building file: ../src/client.cc Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/client.d -MTsrc/client.d -o src/client.o ../src/client.cc Finished building: ../src/client.cc Building target: certificate Invoking: Cross G++ Linker g++ -L/usr/include/openssl -o certificate ./src/certificate.o ./src/client.o ./src/server.o -lssl ./src/client.o: In function `Client::Client()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:12: undefined reference to `X509_REQ_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:13: undefined reference to `X509_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:14: undefined reference to `X509_NAME_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:15: undefined reference to `RSA_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:16: undefined reference to `EVP_PKEY_new' ./src/client.o: In function `Client::~Client()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:24: undefined reference to `X509_REQ_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:25: undefined reference to `X509_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:26: undefined reference to `X509_NAME_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:27: undefined reference to `RSA_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:28: undefined reference to `EVP_PKEY_free' ./src/client.o: In function `Client::GenerateRSAKeyPair()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:34: undefined reference to `RSA_generate_key' ./src/client.o: In function `Client::SetPublicKey()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:40: undefined reference to `EVP_PKEY_assign' ./src/client.o: In function `Client::MakeSignedCertReq(int, int, int)': /home/amirale32/workspace/certificate/Debug/../src/client.cc:46: undefined reference to `X509_REQ_set_pubkey' /home/amirale32/workspace/certificate/Debug/../src/client.cc:50: undefined reference to `EVP_md5' /home/amirale32/workspace/certificate/Debug/../src/client.cc:50: undefined reference to `X509_REQ_sign' ./src/server.o: In function `Server::Server()': /home/amirale32/workspace/certificate/Debug/../src/server.cc:5: undefined reference to `X509_new' /home/amirale32/workspace/certificate/Debug/../src/server.cc:6: undefined reference to `RSA_new' /home/amirale32/workspace/certificate/Debug/../src/server.cc:7: undefined reference to `EVP_PKEY_new' ./src/server.o: In function `Server::~Server()': /home/amirale32/workspace/certificate/Debug/../src/server.cc:15: undefined reference to `X509_free' /home/amirale32/workspace/certificate/Debug/../src/server.cc:16: undefined reference to `RSA_free' /home/amirale32/workspace/certificate/Debug/../src/server.cc:17: undefined reference to `EVP_PKEY_free' ./src/server.o: In function `Server::CreateCertificate(X509_req_st*)': /home/amirale32/workspace/certificate/Debug/../src/server.cc:24: undefined reference to `X509_new' /home/amirale32/workspace/certificate/Debug/../src/server.cc:27: undefined reference to `X509_get_subject_name' /home/amirale32/workspace/certificate/Debug/../src/server.cc:28: undefined reference to `X509_set_issuer_name' /home/amirale32/workspace/certificate/Debug/../src/server.cc:30: undefined reference to `X509_set_subject_name' /home/amirale32/workspace/certificate/Debug/../src/server.cc:31: undefined reference to `X509_REQ_get_pubkey' /home/amirale32/workspace/certificate/Debug/../src/server.cc:33: undefined reference to `X509_gmtime_adj' /home/amirale32/workspace/certificate/Debug/../src/server.cc:34: undefined reference to `X509_gmtime_adj' /home/amirale32/workspace/certificate/Debug/../src/server.cc:35: undefined reference to `EVP_md5' /home/amirale32/workspace/certificate/Debug/../src/server.cc:35: undefined reference to `X509_sign' ./src/server.o: In function `Server::CreateMyCertificate()': /home/amirale32/workspace/certificate/Debug/../src/server.cc:42: undefined reference to `EVP_PKEY_assign' /home/amirale32/workspace/certificate/Debug/../src/server.cc:43: undefined reference to `X509_get_serialNumber' /home/amirale32/workspace/certificate/Debug/../src/server.cc:43: undefined reference to `ASN1_INTEGER_set' /home/amirale32/workspace/certificate/Debug/../src/server.cc:44: undefined reference to `X509_gmtime_adj' /home/amirale32/workspace/certificate/Debug/../src/server.cc:45: undefined reference to `X509_gmtime_adj' /home/amirale32/workspace/certificate/Debug/../src/server.cc:46: undefined reference to `X509_set_pubkey'
RE: compilation error
You also need –lcrypto From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Amir Reda Sent: Friday, September 19, 2014 12:33 AM To: openssl-users@openssl.org Subject: Re: compilation error thx allot for quick reply i have modified the library name to ssl but i have the same problem with the linker error is Building file: ../src/certificate.cpp Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/certificate.d -MTsrc/certificate.d -o src/certificate.o ../src/certificate.cpp Finished building: ../src/certificate.cpp Building file: ../src/client.cc Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/client.d -MTsrc/client.d -o src/client.o ../src/client.cc Finished building: ../src/client.cc Building target: certificate Invoking: Cross G++ Linker g++ -L/usr/include/openssl -o certificate ./src/certificate.o ./src/client.o ./src/server.o -lssl ./src/client.o: In function `Client::Client()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:12: undefined reference to `X509_REQ_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:13: undefined reference to `X509_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:14: undefined reference to `X509_NAME_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:15: undefined reference to `RSA_new' /home/amirale32/workspace/certificate/Debug/../src/client.cc:16: undefined reference to `EVP_PKEY_new' ./src/client.o: In function `Client::~Client()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:24: undefined reference to `X509_REQ_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:25: undefined reference to `X509_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:26: undefined reference to `X509_NAME_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:27: undefined reference to `RSA_free' /home/amirale32/workspace/certificate/Debug/../src/client.cc:28: undefined reference to `EVP_PKEY_free' ./src/client.o: In function `Client::GenerateRSAKeyPair()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:34: undefined reference to `RSA_generate_key' ./src/client.o: In function `Client::SetPublicKey()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:40: undefined reference to `EVP_PKEY_assign' ./src/client.o: In function `Client::MakeSignedCertReq(int, int, int)': /home/amirale32/workspace/certificate/Debug/../src/client.cc:46: undefined reference to `X509_REQ_set_pubkey' /home/amirale32/workspace/certificate/Debug/../src/client.cc:50: undefined reference to `EVP_md5' /home/amirale32/workspace/certificate/Debug/../src/client.cc:50: undefined reference to `X509_REQ_sign' ./src/server.o: In function `Server::Server()': /home/amirale32/workspace/certificate/Debug/../src/server.cc:5: undefined reference to `X509_new' /home/amirale32/workspace/certificate/Debug/../src/server.cc:6: undefined reference to `RSA_new' /home/amirale32/workspace/certificate/Debug/../src/server.cc:7: undefined reference to `EVP_PKEY_new' ./src/server.o: In function `Server::~Server()': /home/amirale32/workspace/certificate/Debug/../src/server.cc:15: undefined reference to `X509_free' /home/amirale32/workspace/certificate/Debug/../src/server.cc:16: undefined reference to `RSA_free' /home/amirale32/workspace/certificate/Debug/../src/server.cc:17: undefined reference to `EVP_PKEY_free' ./src/server.o: In function `Server::CreateCertificate(X509_req_st*)': /home/amirale32/workspace/certificate/Debug/../src/server.cc:24: undefined reference to `X509_new' /home/amirale32/workspace/certificate/Debug/../src/server.cc:27: undefined reference to `X509_get_subject_name' /home/amirale32/workspace/certificate/Debug/../src/server.cc:28: undefined reference to `X509_set_issuer_name' /home/amirale32/workspace/certificate/Debug/../src/server.cc:30: undefined reference to `X509_set_subject_name' /home/amirale32/workspace/certificate/Debug/../src/server.cc:31: undefined reference to `X509_REQ_get_pubkey' /home/amirale32/workspace/certificate/Debug/../src/server.cc:33: undefined reference to `X509_gmtime_adj' /home/amirale32/workspace/certificate/Debug/../src/server.cc:34: undefined reference to `X509_gmtime_adj' /home/amirale32/workspace/certificate/Debug/../src/server.cc:35: undefined reference to `EVP_md5' /home/amirale32/workspace/certificate/Debug/../src/server.cc:35: undefined reference to `X509_sign' ./src/server.o: In function `Server::CreateMyCertificate()': /home/amirale32/workspace/certificate/Debug/../src/server.cc:42: undefined reference to `EVP_PKEY_assign' /home/amirale32/workspace/certificate/Debug/../src/server.cc:43: undefined reference to `X509_get_serialNumber' /home/amirale32/workspace/certificate/Debug/../src/server.cc:43: undefined reference to `ASN1_INTEGER_set' /home/amirale32/workspace/certificate/Debug/../src/server.cc
Re: compilation error
On Fri, Sep 19, 2014 at 3:33 AM, Amir Reda amirale...@gmail.com wrote: thx allot for quick reply i have modified the library name to ssl but i have the same problem with the linker error is Building file: ../src/certificate.cpp Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/certificate.d -MTsrc/certificate.d -o src/certificate.o ../src/certificate.cpp Finished building: ../src/certificate.cpp Building file: ../src/client.cc Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/client.d -MTsrc/client.d -o src/client.o ../src/client.cc Finished building: ../src/client.cc Building target: certificate Invoking: Cross G++ Linker g++ -L/usr/include/openssl -o certificate ./src/certificate.o ./src/client.o ./src/server.o -lssl ./src/client.o: In function `Client::Client()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:12: undefined reference to `X509_REQ_new' ... I believe that should be: g++ -L/usr/lib '-L' is for library paths, not include paths. Additionally, you need to include both libraries in your linker invocation. So it should be: g++ *.o -o myprogr.exe -L/usr/lib -lssl -lcrypto 'ld' is a single pass linker, so the order of '-lss -lcrypto' matters. See the ld(1) man page for details. http://linux.die.net/man/1/ld. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: compilation error
thx allot for reply i have looked at the directory usr/lib i found the folder ssl but i couldn't find the folder of crypto so what can i do On Fri, Sep 19, 2014 at 7:46 PM, Jeffrey Walton noloa...@gmail.com wrote: On Fri, Sep 19, 2014 at 3:33 AM, Amir Reda amirale...@gmail.com wrote: thx allot for quick reply i have modified the library name to ssl but i have the same problem with the linker error is Building file: ../src/certificate.cpp Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/certificate.d -MTsrc/certificate.d -o src/certificate.o ../src/certificate.cpp Finished building: ../src/certificate.cpp Building file: ../src/client.cc Invoking: Cross G++ Compiler g++ -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP -MFsrc/client.d -MTsrc/client.d -o src/client.o ../src/client.cc Finished building: ../src/client.cc Building target: certificate Invoking: Cross G++ Linker g++ -L/usr/include/openssl -o certificate ./src/certificate.o ./src/client.o ./src/server.o -lssl ./src/client.o: In function `Client::Client()': /home/amirale32/workspace/certificate/Debug/../src/client.cc:12: undefined reference to `X509_REQ_new' ... I believe that should be: g++ -L/usr/lib '-L' is for library paths, not include paths. Additionally, you need to include both libraries in your linker invocation. So it should be: g++ *.o -o myprogr.exe -L/usr/lib -lssl -lcrypto 'ld' is a single pass linker, so the order of '-lss -lcrypto' matters. See the ld(1) man page for details. http://linux.die.net/man/1/ld. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org -- Warmest regards and best wishes for a good health,*urs sincerely * *mero*
RE: compilation error
It’s -lssl, not -lopenssl. From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Amir Reda Sent: Thursday, September 18, 2014 1:33 PM To: openssl-users@openssl.org Subject: compilation error /usr/bin/ld: cannot find -lopenssl this is the error when i have tried to compile the code i attached below i install the openssl lib in ubuntu 12.10 i use eclipse and add at the linker setting openssl usr/include/openssl i don't know how to solve this problem please help -- Warmest regards and best wishes for a good health,urs sincerely mero
Re: Compilation Error in application referencing FIPS Object Module using g++
Thanks Stephen I have modified fipsld to compile only fips_premain.c with gcc and my rest of the application is still using g++ for compilation and linking. But I am not able to sort out exactly how to modify the part that will result in embedding signature of exact 40 characters, in case I want to use only g++. On Tue, Mar 8, 2011 at 12:45 AM, Dr. Stephen Henson st...@openssl.orgwrote: On Mon, Mar 07, 2011, raghib nasri wrote: Do you mean to say I should modify fipsld to use gcc for compiling fips_premain.c. Or is there any way to still use g++ for my application with minimal change in fipsld. Please suggest. Well two options, one is to change it to use gcc just for the compilation of fips_premain.c, the other is to modify the part that embeds the signature so it uses 40 characters instead of 40+1 null. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Compilation Error in application referencing FIPS Object Module using g++
On Wed, Mar 09, 2011, raghib nasri wrote:
Thanks Stephen
I have modified fipsld to compile only fips_premain.c with gcc and my rest
of the application is still using g++ for compilation and linking. But I am
not able to sort out exactly how to modify the part that will result in
embedding signature of exact 40 characters, in case I want to use only g++.
Well this in untested...
The fipsld script embeds the signature in fips_premain.c by setting the
preprocessor symbol HMAC_SHA1_SIG. The normal format we have is
40 hex digits which ends up with 40 characters and the extra null.
If you modify that to an alternative format such as...
{'a','0','c',...}
with exactly 40 characters it should work.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager majord...@openssl.org
Re: Compilation Error in application referencing FIPS Object Module using g++
Now I don't think its possible. I am statically linking application with
object module and library and if you have observed fipsld, first time its
compiling and linking the application without any preprocessor symbol. At
that time fips_premain.c observes that no HMAC defined and generates the 40
char HMAC that serves as output for the application (for the first time
compilation only.) In fipsld, this output is assigned to SIG variable and
for later stage compilation , SIG is assigned to preprocessor symblo
HMAC_SHA1_SIG. And now premain.c behaves in different way since HMAC defined
now. So ultimately there is nothing to change in fipsld to get 40 chars HMAC
and I have to depend on gcc for fips_premain.c compilation. Well thanks
Stephen for your interest and guidance and if you to make some correction
please convey.
On Wed, Mar 9, 2011 at 8:51 PM, Dr. Stephen Henson st...@openssl.orgwrote:
On Wed, Mar 09, 2011, raghib nasri wrote:
Thanks Stephen
I have modified fipsld to compile only fips_premain.c with gcc and my
rest
of the application is still using g++ for compilation and linking. But I
am
not able to sort out exactly how to modify the part that will result in
embedding signature of exact 40 characters, in case I want to use only
g++.
Well this in untested...
The fipsld script embeds the signature in fips_premain.c by setting the
preprocessor symbol HMAC_SHA1_SIG. The normal format we have is
40 hex digits which ends up with 40 characters and the extra null.
If you modify that to an alternative format such as...
{'a','0','c',...}
with exactly 40 characters it should work.
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http://www.openssl.org
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager majord...@openssl.org
Re: Compilation Error in application referencing FIPS Object Module using g++
On Mon, Mar 07, 2011, raghib nasri wrote: Hi, I am using FIPS Object Module and encountered an error while compiling my application using g++. ?fips_premain.c:71: error: initializer-string for array of chars is too long? I cannot change fips_premain.c since its part of FIPS validation I guess. Please suggest any sollution. Although you can't modify fips_premain.c you can modify fipsld: which doesn't have to the be the standard one as long as it follows the rules in the security policy. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Compilation Error in application referencing FIPS Object Module using g++
Do you mean to say I should modify fipsld to use gcc for compiling fips_premain.c. Or is there any way to still use g++ for my application with minimal change in fipsld. Please suggest. On Mon, Mar 7, 2011 at 9:15 PM, Dr. Stephen Henson st...@openssl.orgwrote: On Mon, Mar 07, 2011, raghib nasri wrote: Hi, I am using FIPS Object Module and encountered an error while compiling my application using g++. ?fips_premain.c:71: error: initializer-string for array of chars is too long? I cannot change fips_premain.c since its part of FIPS validation I guess. Please suggest any sollution. Although you can't modify fips_premain.c you can modify fipsld: which doesn't have to the be the standard one as long as it follows the rules in the security policy. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Compilation Error in application referencing FIPS Object Module using g++
On Mon, Mar 07, 2011, raghib nasri wrote: Do you mean to say I should modify fipsld to use gcc for compiling fips_premain.c. Or is there any way to still use g++ for my application with minimal change in fipsld. Please suggest. Well two options, one is to change it to use gcc just for the compilation of fips_premain.c, the other is to modify the part that embeds the signature so it uses 40 characters instead of 40+1 null. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: compilation error building openssl-0.9.8k
On Thu, May 28, 2009, Vivek Subbarao wrote: Hi I am getting the below mentioned compilation error when i try to build openssl-0.9.8k using visual studio 2008. C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\sal.h(1984) : fatal error RC22105: MultiByteToWideChar failed. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\r c.EXE' : return code '0x1' Stop. i am on windows server 2003 sp2 32-bit. The commands i executed at the prompt to build openssl are perl Configure VC-WIN32 --prefix=c:\openssl Use a / instead of a \ in the --prefix option. This is fixed in more recent snapshots but for now causes problems. Steve. -- Dr Stephen N. Henson. Email, S/MIME and PGP keys: see homepage OpenSSL project core developer and freelance consultant. Homepage: http://www.drh-consultancy.demon.co.uk __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: compilation error building openssl-0.9.8k
I had no problems with this Visual Studio 9.0 on XP SP 3. Do you do: nmake -f ms\ntdll.mak before the nmake -f ms\ntdll.mak install ? Carter Carter Browne CBCS cbro...@cbcs-usa.com 781-721-2890 Vivek Subbarao wrote: Hi I am getting the below mentioned compilation error when i try to build openssl-0.9.8k using visual studio 2008. C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\sal.h(1984) : fatal error RC22105: MultiByteToWideChar failed. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\r c.EXE' : return code '0x1' Stop. i am on windows server 2003 sp2 32-bit. The commands i executed at the prompt to build openssl are perl Configure VC-WIN32 --prefix=c:\openssl ms\do_masm nmake -f ms\ntdll.mak install pls help me to get openssl built and working. Thanks __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
RE: compilation error building openssl-0.9.8k
Yes i think i did. But then next time i tried build using nmake -f ms\ntdll.mak install And the same error occurred. -Original Message- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Carter Browne Sent: 28 May 2009 20:47 To: openssl-users@openssl.org Subject: Re: compilation error building openssl-0.9.8k I had no problems with this Visual Studio 9.0 on XP SP 3. Do you do: nmake -f ms\ntdll.mak before the nmake -f ms\ntdll.mak install ? Carter Carter Browne CBCS cbro...@cbcs-usa.com 781-721-2890 Vivek Subbarao wrote: Hi I am getting the below mentioned compilation error when i try to build openssl-0.9.8k using visual studio 2008. C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\sal.h(1984) : fatal error RC22105: MultiByteToWideChar failed. NMAKE : fatal error U1077: 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\r c.EXE' : return code '0x1' Stop. i am on windows server 2003 sp2 32-bit. The commands i executed at the prompt to build openssl are perl Configure VC-WIN32 --prefix=c:\openssl ms\do_masm nmake -f ms\ntdll.mak install pls help me to get openssl built and working. Thanks __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager majord...@openssl.org
Re: Compilation error using Openssl 0.9.8c in Ubuntu Feisty
Thanks for your quick answer David, I will think about use IDEA instead of AES (i believe that´s no problem about commercial use with AES). Regards. David Schwartz escribió: I´m adapting a PKCS#11 module for using it on Ubuntu Feisty. I had it perfectly working on Ubuntu Dapper, but when I compile it (using g++ 4.1.2-0ubuntu4 and Kdevelop 3.5.6) and compiler reaches to the call EVP_idea_cbc(), it shows me this error: 'EVP_idea_cbc' was not declared in this scope. I´ve looked at evp.h file and I found that: #ifndef OPENSSL_NO_IDEA ... const EVP_CIPHER *EVP_idea_cbc(void); ... #endif ¿Is possible that constant OPENSSL_NO_IDEA could be pre-defined? ¿Somebody could help me to solve this issue? I believe there are some legal issues with using the IDEA algorithm (patented by Ascom). If you know that it is legal for you do so, you can recompile OpenSSL with the IDEA algorithm included. If your use is non-commercial, I believe you are okay as Ascom has granted permission for this use. DS __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED] __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
RE: Compilation error using Openssl 0.9.8c in Ubuntu Feisty
I´m adapting a PKCS#11 module for using it on Ubuntu Feisty. I had it perfectly working on Ubuntu Dapper, but when I compile it (using g++ 4.1.2-0ubuntu4 and Kdevelop 3.5.6) and compiler reaches to the call EVP_idea_cbc(), it shows me this error: 'EVP_idea_cbc' was not declared in this scope. I´ve looked at evp.h file and I found that: #ifndef OPENSSL_NO_IDEA ... const EVP_CIPHER *EVP_idea_cbc(void); ... #endif ¿Is possible that constant OPENSSL_NO_IDEA could be pre-defined? ¿Somebody could help me to solve this issue? I believe there are some legal issues with using the IDEA algorithm (patented by Ascom). If you know that it is legal for you do so, you can recompile OpenSSL with the IDEA algorithm included. If your use is non-commercial, I believe you are okay as Ascom has granted permission for this use. DS __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
