Artimus has asked for the wisdom of the Perl Monks concerning the following question:

Hi monks!

Have a problem with IO::Socket::SSL on my Raspberry Pi. After I enter

sudo cpanm IO::Socket::SSL

It takes it quite a lot to think. But finally it returns me an error that installation failed.

With sudo cat /root/.cpanm/build.log in the end of log I can see:
Test Summary Report + + ------------------- + + t/nonblock.t (Wstat: 0 Tests: 27 Failed: 2) + + Failed tests: 13, 26 + + Files=37, Tests=771, 235 wallclock secs ( 3.92 usr 0.46 sys + 168.58 +cusr 6.64 csys = 179.60 CPU) + Result: FAIL + + Failed 1/37 test programs. 2/771 subtests failed. + + Makefile:783: recipe for target 'test_dynamic' failed + + make: *** [test_dynamic] Error 255 + + -> FAIL Installing IO::Socket::SSL failed. See /root/.cpanm/build.log +for details.

I am trying to make a simple e-mail notifier with Mail::IMAPClient, IO::Socket::SSL and Device::BCM2835{the last one is used to interact with GPIO}

Seeking for advice how to solve the problem with module installation{would it be right, for example, to force installation via "cpan" instead of cpanminus?}or artelnatives to it.

With respect, Artimius.

Replies are listed 'Best First'.
Re: IO::Socket::SSL and raspberry
by Corion (Patriarch) on Jul 24, 2015 at 15:32 UTC
    FAIL Installing IO::Socket::SSL failed. See /root/.cpanm/build.log for + details.

    So, what does /root/.cpanm/build.log say about t/nonblock.t failing? How does that test fail?

      look a little bit more carefully at what I cat before:) It is this file itself!

        Yes, but what you posted only shows the summary, not how the test failed.

        If there is no further informaion in the log about how the test failed, run the test manually:

        cpanm --look IO::Socket::SSL perl Makefile.PL make make test perl -Mblib -w t/nonblock.t

        Maybe the test output tells you an easy reason why it failed.

Re: IO::Socket::SSL and raspberry
by kevbot (Vicar) on Jul 26, 2015 at 00:42 UTC
    Hi Artimus,

    I see that Corion likely identified the bug you ran into in this node Re^7: IO::Socket::SSL and raspberry.

    I just wanted to offer one more datapoint. IO::Socket::SSL installed fine on my raspberry pi. I have the following setup:

    • Model B Revision 2.0, 512 MB (Hardware Revision: 000e).
    • Raspbian Weezy, with most up-to-date versions of openssl and libssl-dev installed
    • perl 5.20.1, installed with perlbrew and compiled with -Dusethreads
    • Installed IO::Socket::SSL using cpanm

    This thread made me realize that I had not played around with my pi for a while. I think I'll start tinkering with it again.

Re: IO::Socket::SSL and raspberry
by poj (Abbot) on Jul 24, 2015 at 17:30 UTC

    Which OS ?

    It installed OK on my Pi2

    Linux raspberrypi2 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53:55 GMT 2015 armv7l GNU/Linux
    poj

      I have my Pi B+... it is raspbian

      Two mistakes "multiple write attempt" shown by tests that are stopping installation. It happens to have not cutting-edge hardware))

        It might be that your system is way slower as expected and thus runs into unexpected conditions or that some other issues make the tests for non-blocking fail. Since these care only about the behavior of non-blocking sockets you might simply force the install, at least unless your program depends on fully working non-blocking behavior.