in reply to Crypt::SSLeay problem after upgrading to 5.10

Hmm, well, I maintain Crypt::SSLeay and I did take care to check that it builds correctly with 5.10 (well, to be honest, I haven't had the time to check with the official 5.10 build, but I tracked bleadperl since I took over the maintenance).

The "this looks like a Debian host" message in the output from Makefile.PL is something I added based on feedback from another Debian user, who tracked down the library dependency problem.

From what I can see here, it doesn't look like Crypt::SSLeay per se is at fault, but rather the 1:1.2.3-6ubuntu4 versus 1:1.2.3-13ubuntu2 issue that needs to be resolved. Nevertheless, if I can be of help, feel free to open a ticket on the RT queue.

• another intruder with the mooring in the heart of the Perl

  • Comment on Re: Crypt::SSLeay problem after upgrading to 5.10

Replies are listed 'Best First'.
Re^2: Crypt::SSLeay problem after upgrading to 5.10
by jkeenan1 (Deacon) on Dec 21, 2007 at 12:32 UTC
    Further evidence that this is a dependency problem: I just managed to successfully upgrade on Darwin with 5.10. The upgrade was successful except for this one warning thrown repeatedly during make test:

    t/00-basic......ok 7/12Use of uninitialized value $owner in substituti +on (s///) at /usr/local/lib/perl5/site_perl/5.8.7/darwin-2level/Pod/C +overage.pm line 288.
    Jim Keenan
Re^2: Crypt::SSLeay problem after upgrading to 5.10
by jkeenan1 (Deacon) on Dec 21, 2007 at 12:21 UTC

    Yes, I too believe that this is more of a dependency problem than a problem with the Perl module per se -- but these seem to be endemic with this module. I recall having great difficulty trying to install it on Win32 last year. But I know it was previously working on this very same Ubuntu box with 5.8.

    Jim Keenan
Re^2: Crypt::SSLeay problem after upgrading to 5.10
by jkeenan1 (Deacon) on Jan 07, 2008 at 19:21 UTC
    1. Grinder: I didn't see almut's Dec 21 posting until today. Does that indicate problems in the module?

    2. In the last few weeks I've had to re-install modules that contain XS code on each of three boxes. Often I've had a program fail because some module inside of some other module needed an upgrade -- most frequently, HTML::Parser. I've managed to get all the modules I needed upgraded on all three boxes -- except this case of Crypt::SSLeay on Ubuntu.

    Jim Keenan