in reply to Re^3: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
in thread ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003

Since you've asked, here is a console log from how I got things to work.

It is just easier to do thing manually (Note:many of the commands are wrapped for posting): 

C:\Perl510\packages\Crypt-SSLeay-0.57>del *.obj *.dll

C:\Perl510\packages\Crypt-SSLeay-0.57>
cl -MT -LD -I c:\perl510\lib\CORE\ -I c:\openssl\include\ -DWIN32 SSLe
+ay.c 
ssleay.def perl510.lib libeay32mt.lib ssleay32mt.lib 
-link 
-LIBPATH:c:\cl\lib\ 
-LIBPATH:c:\perl510\lib\CORE\ 
-LIBPATH:c:\OpenSSL\lib\vc\

Microsoft (R) 32-bit C/C++ Standard Compiler Version 13.00.9466 for 80
+x86
Copyright (C) Microsoft Corporation 1984-2001. All rights reserved.

SSLeay.c
Microsoft (R) Incremental Linker Version 7.00.9466
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:SSLeay.dll
/dll
/implib:SSLeay.lib
-LIBPATH:c:\cl\lib\
-LIBPATH:c:\perl510\lib\CORE\
-LIBPATH:c:\OpenSSL\lib\vc\
/def:ssleay.def
SSLeay.obj
perl510.lib
libeay32mt.lib
ssleay32mt.lib
   Creating library SSLeay.lib and object SSLeay.exp

C:\Perl510\packages\Crypt-SSLeay-0.57>
md \perl510\site\lib\auto\Crypt\SSLeay

C:\Perl510\packages\Crypt-SSLeay-0.57>
copy SSLeay.dll \perl510\site\lib\auto\Crypt\SSLeay
        1 file(s) copied.

C:\Perl510\packages\Crypt-SSLeay-0.57>
md \perl510\site\lib\Crypt

C:\Perl510\packages\Crypt-SSLeay-0.57>
copy SSLeay.pm \perl510\site\lib\Crypt
        1 file(s) copied.

C:\Perl510\packages\Crypt-SSLeay-0.57>
xcopy /s lib \Perl510\site

lib\Crypt\SSLeay\Conn.pm
lib\Crypt\SSLeay\CTX.pm
lib\Crypt\SSLeay\Err.pm
lib\Crypt\SSLeay\MainContext.pm
lib\Crypt\SSLeay\X509.pm
lib\Net\SSL.pm
6 File(s) copied

C:\Perl510\packages\Crypt-SSLeay-0.57>
\Perl510\bin\perl5.10.0.exe -MCrypt::SSLeay -wle"print $Crypt::SSLeay:
+:VERSION"

0.57

[download]
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re^4: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
  • Download Code

Replies are listed 'Best First'.
Re^5: ActiveState Perl 10.x and Crypt::SSLeay not installed errors on Windows 2003
by yeah (Novice) on Mar 29, 2008 at 02:39 UTC
    Ok last question. Where did you find the source for Crypt::SSLeay? All I can find is the pre-built distribution.
[reply]
      Where did you find the source for Crypt::SSLeay?

      Just follow the first link at Crypt::SSLeay.

      (I really think you might be best advised to work through the ppm problem instead.)

      Cheers,
      Rob
[reply]

        Unfortunately, the PPM problem seems to run deeper than just the problem with the errant ppds at uwinnipeg. I also tried the 5.10 PPD at bribes, which at least appears to be a proper PPD, but when I try and install it: 

        C:\Perl510\bin>ppm-shell
ppm 4.01
Copyright (C) 2007 ActiveState Software Inc.  All rights reserved.
ppm> config list
arch = MSWin32-x86-multi-thread-5.10
gui.filter =
gui.filter.fields = name
gui.filter.type = all
gui.geometry = 568x535+364+272
gui.install_area = site
gui.view.abstract = 1
gui.view.area = 1
gui.view.author = 0
gui.view.available = 1
gui.view.installed = 1
gui.view.name = 1
gui.view.repo = 1
gui.view.sortcolumn = name
gui.view.sortorder = -increasing
gui.view.statusbar = 1
gui.view.toolbar = 1
ppm> install http://www.bribes.org/perl/ppm/Crypt-SSLeay.ppd
ppm install failed: The PPD does not provide code to install for this 
+platform
ppm> quit


C:\Perl510\bin>lwp-request http://www.bribes.org/perl/ppm/Crypt-SSLeay
+.ppd
<SOFTPKG NAME="Crypt-SSLeay" VERSION="0,57,0,0">
        <TITLE>Crypt-SSLeay</TITLE>
        <ABSTRACT>OpenSSL support for LWP</ABSTRACT>
        <AUTHOR>David Landgren (david@landgren.net)</AUTHOR>
        <IMPLEMENTATION>
                <OS NAME="MSWin32" />
                <ARCHITECTURE NAME="MSWin32-x86-multi-thread" />
                <CODEBASE HREF="Crypt-SSLeay-0.57-PPM56.tar.gz" />
        </IMPLEMENTATION>
        <IMPLEMENTATION>
    <OS NAME="MSWin32" />
    <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.8" />
    <CODEBASE HREF="Crypt-SSLeay-0.57-PPM58.tar.gz" />
  </IMPLEMENTATION>
  <IMPLEMENTATION>
    <OS NAME="MSWin32" />
    <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.10" />
    <CODEBASE HREF="Crypt-SSLeay-0.57-PPM510.tar.gz" />
  </IMPLEMENTATION>
</SOFTPKG>

        [download]

        This string: 

        arch = MSWin32-x86-multi-thread-5.10

        [download]

        seems to match this one: 

            <ARCHITECTURE NAME="MSWin32-x86-multi-thread-5.10" />

        [download]

        so on the basis of what information is PPM deciding that The PPD does not provide code to install for this platform? I made a half hearted attempt to work through the internals of ppm to discover that, but got lost.

        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom