RE: libcrypto.a linking problem?

2013-03-18 Thread Floodeenjr, Thomas
@openssl.org Subject: libcrypto.a linking problem? I'm unable to build Git 1.8.1.3 with libcrypto. I've compiled and built OpenSSL with the same LDFLAGS and CPPFLAGS as below. I also have a `/etc/ld.so.conf.d/sandbox.conf` file which loads `/sandbox/builds/lib` as a librar

libcrypto.a linking problem?

2013-03-18 Thread zero modulo
I'm unable to build Git 1.8.1.3 with libcrypto. I've compiled and built OpenSSL with the same LDFLAGS and CPPFLAGS as below. I also have a `/etc/ld.so.conf.d/sandbox.conf` file which loads `/sandbox/builds/lib` as a library path for LD_LIBRARY_PATH. $ uname -a Linux kosuna 3.5.0-17-generic #28-Ubu

FIPS module with C++ linking problem

2006-04-13 Thread Crane, Rebecca-P56400
Title: FIPS module with C++ linking problem Hello, I am having an issue that hopefully someone can help with! I am trying to use OpenSSL FIPS (OpenSSL-fips-1.0.tar.gz) and am having difficulty. My program is developing in C++, and this is causing problems with fipsld. I built it on Solaris

Re: Linking problem on Solaris 8

2001-07-16 Thread Richard Levitte - VMS Whacker
From: Carson Gaspar <[EMAIL PROTECTED]> carson> > sed -e carson> > 's,^\("solaris[^"]*-gcc.*\):gnu-shared:\(.*$\),\1:solaris-shared:\2,' Con carson> > figure > Configure.fixed carson> > carson> > and all should be well. carson> carson> That was me. And I'm rather sad that this didn't make it int

Re: Linking problem on Solaris 8

2001-07-16 Thread Richard Hopkins
Yes - I've seen this. Searching through the archives I found a message explaining the problem (sorry, can't credit the original poster off the top of my head). Basically... sed -e 's,^\("solaris[^"]*-gcc.*\):gnu-shared:\(.*$\),\1:solaris-shared:\2,' Con figure > Configure.fixed and all shoul

RE: Linking Problem on Solaris8

2001-07-13 Thread Brad McNamara
It seems that the 'config/Configure' script is incorrectly guessing which kind of shared library to build for OpenSSL 0.9.6b on Solaris8. When 'config threads shared' is invoked, the 'Makefile' created has the variable "SHLIB_TARGET" set to "gnu-shared" when it should be set to "solaris-share

Re: Linking problem on HP

2001-04-19 Thread Lutz Jaenicke
On Thu, Apr 19, 2001 at 01:35:13PM -0400, Monique Mandala wrote: > /usr/ccs/bin/ld: Unsatisfied symbols: >X509_NAME_oneline (code) >SSL_accept (code) >RAND_seed (code) >SSL_set_fd (code) >SSL_library_init (code) >ERR_get_error (code) >SSL_CTX_set_verify (code) > etc. >

Linking problem on HP

2001-04-19 Thread Monique Mandala
I have written a Server program that works on NT and AIX, but when I install openssl on HP and try to run the compile script, I get the following error message: /usr/ccs/bin/ld: Unsatisfied symbols: X509_NAME_oneline (code) SSL_accept (code) RAND_seed (code) SSL_set_fd (code) SSL_l

Re: linking problem

2000-08-05 Thread Kervin Pierre
I'm not sure if that's your problem but, you may need to patch the openssl source. Actually I just went through this. RAND_egd is defined in libssl but RAND_egd_bytes is not. It is supplied by FixPatch script. Download and extract openssl in same parent dir as apache-ssl. Run FixPatch as usu

Re: linking problem

2000-08-05 Thread Craig Shaver
Looks like you are adding mod_perl also. Did you try to build without mod_perl? Take out the added modules until you find out what is causing the problem. Robert Kubarych wrote: > > While running make on apache_1.3.12 it exits with the following error: > > ld: > Unresolved: > RAND_egd_bytes > *

linking problem

2000-08-05 Thread Robert Kubarych
While running make on apache_1.3.12 it exits with the following error: ld: Unresolved: RAND_egd_bytes *** Exit 1 Stop. *** Exit 1 Stop. *** Exit 1 Stop. Our platform is Tru64 4.0f. Previous to running make I ran: root#./configure --activate-module=src/modules/perl/libperl.a \ > --activate-modu

Linking problem building 0.9.4 debug?

2000-01-25 Thread Grebelsky, Konstantin
I am trying to build a debug dlls using 32all.bat but getting linking problems below.. What is wrong? Does anybody know? Should I be using 32all.bat at all? If not what are the steps that are needed. For the regular build I am following the steps in install.w32 .\crypto\objects\obj_dat.h