"Scott R. Every" <[EMAIL PROTECTED]> writes:
> you can get it [RSAref] from...
Thanks.
I compiled it and linked against it according to ssleay "method 2":
Eric> The second method is to build as per normal and link applications with
Eric> the RSAglue library. The correct library order would be
Eric> cc -o cmd cmd.o -lssl -lRSAglue -lcrypto -lrsaref -ldes
Eric> The RSAglue library is built in the rsa directory and is NOT
Eric> automatically installed.
To do this I modified Net::SSLeay Makefile.PL to read (starting around
line 55 or so (in my development sources)):
WriteMakefile(
'NAME' => 'Net::SSLeay',
'VERSION_FROM' => 'SSLeay.pm', # finds $VERSION
'DEFINE' => '', # e.g., '-DHAVE_SOMETHING'
'DISTNAME' => 'Net_SSLeay.pm',
'dist' => { COMPRESS => 'gzip', SUFFIX => 'gz', },
'LIBS' => ["-L$ssleay_path -L$ssleay_path/lib -lssl -lRSAglue -lcrypto
-lrsaref"],
'INC' => "-I$ssleay_path/include",
);
Note the libraries as per Eric's instructions. Then just build as usual.
All works like a charm - or at least `make test' passes OK.
As it was so easy to get it working, I'll include RSAref support out
of box in the next release.
--Sampo
P.S. The platform used to make this test was:
* openssl-0.9.2 (prerelease from rsync CVS as announced
by Ralf Engelschall on the mailing list)
* Net_SSLeay.pm-1.03 + some fixes that shouldn't affect this issue
* egcs-2.91.60
* perl5.005_02
* Linux 2.0.36 (RH 5.1)
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
