Hi,

I am trying to set up apache w/ mod_ssl, following the install guide on the web:
http://www.engelschall.com/sw/mod_ssl/distrib/mod_ssl-SNAP/INSTALL

My system is RHL5.2 on AMD K6-2.  And I am using apache_1.3.4, mod_ssl-2.2.4-1.3.4,
rsaref-2.0, openssl0.9.1c (w/ its patch) and nothing else.
I did not modify rsaref-2.0/source/global.h file ('cause I didn't know how I should 
change it for my platform)

Following the above mentioned guide, I did 'make' on openssl_0.9.1c , and received
the following error messages.  I don't know what to do now..... Please help!


/bin/rm -f ssleay
gcc -o ssleay -DMONOLITH -I../include -DRSAref -O3 ssleay.o verify.o asn1pars.o req.o 
dgst.o dh.o enc.o gendh.o errstr.o ca.o pkcs7.o crl2p7.o crl.o rsa.o dsa.o dsaparam.o 
x509.o genrsa.o s_server.o s_client.o speed.o s_time.o apps.o s_cb.o s_socket.o 
version.o sess_id.o ciphers.o -L. -L.. -L../.. -L../../.. -L.. -lssl -L.. -lcrypto 
-lRSAglue -Lpwd/../rsaref-2.0/local/ -lrsaref 
ld: cannot open -lrsaref: No such file or directory
make[1]: *** [ssleay] Error 1
make[1]: Leaving directory `/home/down/openssl-0.9.1c/apps'
making test...
make[1]: Entering directory `/home/down/openssl-0.9.1c/test'
gcc -I../include -DRSAref -O3   -c bntest.c -o bntest.o
gcc -o bntest -I../include -DRSAref -O3 bntest.o -L. -L.. -L../.. -L../../.. -L.. 
-lcrypto -lRSAglue -Lpwd/../rsaref-2.0/local/ -lrsaref 
ld: cannot open -lrsaref: No such file or directory
make[1]: *** [bntest] Error 1
make[1]: Leaving directory `/home/down/openssl-0.9.1c/test'
making tools...
make[1]: Entering directory `/home/down/openssl-0.9.1c/tools'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/down/openssl-0.9.1c/tools'
[root@ny1 openssl-0.9.1c]# 


Thanks in advance,

- Heewoon Chung
[EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl)   www.engelschall.com/sw/mod_ssl/
Official Support Mailing List               [EMAIL PROTECTED]
Automated List Manager                       [EMAIL PROTECTED]

Reply via email to