Tran Duc Trung <[EMAIL PROTECTED]> writes:

> Miguel �ngel Monjas Llorente <[EMAIL PROTECTED]> writes:
> > Any clue?
> 
> I had to modify Makefile.PL to be able to compile
> 
> 1) added .exe suffix to the test of executability of openssl
> 
> orig:
>     until (-x "$openssl_path/bin/openssl") {
> mine:
>     until (-x "$openssl_path/bin/openssl.exe") {

Makes sense.

> 
> 2) near the end of the file I ignored the comments regarding WIN32,
>    commented out the LIBS lines and added this line
> 
> 'MYEXTLIB'    => "$openssl_path/lib/ssleay32.lib $openssl_path/lib/libeay32.lib",

Ok.

> After that it compiles. 'nmake test' also almost okay except the
> test which requires fork() and the 'Making self signed certificate
> just for these tests' section in test.pl, which has the line
> 
>     system "examples/makecert.pl examples $ssleay_path $silent";
> 
> Win32 is not UNIX, hash bang does not work here. So I changed it to
> 
>     system "perl examples/makecert.pl examples $ssleay_path $silent";
> 
> or probably even better is
> 
>     system "$^X examples/makecert.pl examples $ssleay_path $silent";

True.

Now, could you provide me a snippet showing how I can discover in Perl
that I am running on Windows platform. That way Makefile.PL will be
able to automatically adapt.

Also, please let me know which Visual C++ (if any) you used. It seems
the strictness of error checking varies between versions.

Look forward to these fixes being integrated in 1.06.

--Sampo
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to