On Fri, Mar 10, 2000 at 04:58:05PM -0600, Ben Lindstrom
wrote:>
>
> On Fri, 10 Mar 2000, Mate Wierdl wrote:
>
> [..]
> >
> > My libs are
> >
> > /space/local/lib/libRSAglue.a
> > /space/local/lib/libcrypto.a
> > /space/local/lib/libssl.a
> >
> > my includes are in
> >
> > /space/local/include/openssl
> >
> > so could you recommend a `./configure' line?
> >
> Ermm... Since the headers are kinda in non-standard location
Well, this is the directory setup in the openssl rpm (I am trying to
adopt the rpm to solaris).
> I can't realy give a good suggestion
>
> Only suggestion (assuming it takes) is to do a:
>
> CFLAGS="-I/space/local/include/openssl"; export CFLAGS
> configure --with-ssl-dir=/space/local
>
> (Assuming the patch was applied to ./configure)
Which patch do you mean? I am just using the tarball for 1.2.2p1.
In any case, it seems to me that the problem is not not finding the
include or lib files: in config.log, I see
configure:1891: checking for OpenSSL/SSLeay directory
configure:1918: gcc -o conftest -I/space/local/include -L/usr/ucblib
conftest.c -ldl -lsocket -lnsl -lz -L/space/local/lib -lpam -lcrypto 1>&5
/space/local/lib/libcrypto.a(rsa_lib.o): In function `RSA_new_method':
/space/local/src/redhat/BUILD/wierdlm/openssl-0.9.4/crypto/rsa/rsa_lib.c:109:
unde
fined reference to `RSA_PKCS1_RSAref'
collect2: ld returned 1 exit status
configure: failed program was:
#line 1906 "configure"
#include "confdefs.h"
#include <openssl/rsa.h>
#include <openssl/bn.h>
#include <openssl/sha.h>
int main(void)
{RSA *key; char seed[2048];memset(seed, 0,
#sizeof(seed));
RAND_seed(seed,
#sizeof(seed));key=RSA_generate_key(32,3,NULL,NULL);
return(key==NULL);}
So the gcc line seem to be correct.
I'd like to add, that
1.2.2 works with openssl-0.9.4
but
1.2.2 does not work with openssl-0.9.4 (above configure problem)
1.2.2p1 does not work with openssl-0.9.{4,5} (above configure problem)
The reason I am trying to use openssl-0.9.5 is that somebody mentioned
a leak (related to the random device) on solaris when using 0.9.4, and
supposedly this leak is fixed in 0.9.5.
Mate