> I've been trying to get version 1.05 of the Net::SSLeay Perl module
> interface to OpenSSL to build with version 0.9.5a of OpenSSL.
> So far I've
> been hitting a lot of problems (I'm actually doing this under NT with
> ActiveState Perl 5.005_03, but most of the problems that I've
> solved so far
> look like they would equally be problems under UNIX: e.g.
> SSLeay.c includes
> some Perl header files which define "mod", "seed", and "list", which
> confuses various of the OpenSSL header files).
>
> Is there anyone here who has managed to get this combination
> to work (either
> on UNIX or on NT)? If so, how did you do it?
>
> --Roger Dearnaley <[EMAIL PROTECTED]>
The next major problem I've run into is that all the C function definitions
in the SSLeay.xs file in Net::SSLeay (from which the SSLeay.c file is
automagically generated) are in old K&R form, which is not ANSI-compliant.
This would be OK but for the fact that Visual C++ is being called with the
-TP flag which tells it to go into C++ mode, including requiring
ANSI-compliant function definitions, and that replacing this with the -TC
flag to force it back into C mode causes a bunch of stuff in various
Perl-related header files that are being included to blow up. The obvious
solution is to edit the SSLeay.xs file by hand into ANSI-compliant form,
which I can do, but I really hate to have to list as part of an installation
procedure. The ideal solution would be for whoever is currently maintaining
Net::SSLeay to fix this and bring out a new version.
I've also tried linking against OpenSSL 0.9.6, and it didn't help.
--Roger Dearnaley <[EMAIL PROTECTED]>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
