Hello again,

I have now written thousands of line of perl and have been having a great time. Having delivered several products, I am now attempted a ground up build based on strawberry since my previous build was an inherited activestate version.

That said, I have strawberry installed, path updated, etc. I want to install Win32API::CommPort using cpanm and it consistently fails. Tried install Win32API::SerialPort first, same result. I tested com1 it works. I put a loopback on pins 2-3, still fails.

terminal shows

c:\strawberry>cpanm Win32::SerialPort

--> Working on Win32::SerialPort

Fetching http://www.cpan.org/authors/id/B/BB/BBIRTH/Win32-SerialPort-0.22.tar.gz ... OK

Configuring Win32-SerialPort-0.22 ... OK

Building and testing Win32-SerialPort-0.22 ... FAIL

! Installing Win32::SerialPort failed. See \.cpanm\build.log for details.

from the log file it get...

Test Summary Report

-------------------

t/test1.t (Wstat: 1280 Tests: 309 Failed: 5)

Failed tests: 53, 57, 61, 210, 219

Non-zero exit status: 5

t/test2.t (Wstat: 768 Tests: 146 Failed: 3)

Failed tests: 5-7

Non-zero exit status: 3

t/test3.t (Wstat: 768 Tests: 264 Failed: 3)

Failed tests: 40, 44, 48

Non-zero exit status: 3

t/test4.t (Wstat: 3072 Tests: 518 Failed: 12)

Failed tests: 5-7, 83-85, 232-234, 294-296

Non-zero exit status: 12

Files=7, Tests=1808, 59 wallclock secs ( 0.22 usr + 0.08 sys = 0.30 CPU)

Result: FAIL

Failed 4/7 test programs. 23/1808 subtests failed.

dmake.exe: Error code 255, while making

'test_dynamic'

-> FAIL Installing Win32API::CommPort failed. See \.cpanm

\build.log for details.

I made great use of the serial ports on my activestate install, but am really interested in getting this going on strawberry. Also, I installed Win32::API just fine.

Any hints???

In reply to win32api::commport install fails by ccherri

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.