This is the mail archive of the
mailing list for the Cygwin project.
RE: Perl with SerialPort
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 13 Feb 2008 23:07:32 -0000
- Subject: RE: Perl with SerialPort
- References: <email@example.com>
On 13 February 2008 22:59, Dave Korn wrote:
> On 13 February 2008 22:46, Dave Korn wrote:
>> On 13 February 2008 21:23, curator wrote:
>>> So the question is: i would like to prefer no 2. For that i have to
>>> install SerialPort for Perl for cygwin.
>>> Is this possible, and if yes, could you tell me how?
>> I'm no perl expert,
> Still true, but I've found one thing out since sending that:
Still true, but I've found another:
> Running make test
> /usr/bin/perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0,
> 'blib/lib', 'blib/arch')" t/*.t
> t/01timing.............ok 4/7
> t/01timing.............NOK 7# Failed test (t/01timing.t at line 33)
> # then: 207441765 now: 207443905 diff: 2140
> # Looks like you failed 1 test of 7.
That diff is absolutely reliably consistently 2140 for me. I'd speculate
that maybe the cygwin signal emulation requires a context switch or two, to or
away from the signal processing thread, and so we're seeing an extra quantum
or two of constant overhead for systematic reasons. So...
> looking at 01timing.t:-
Well, editing it in ~/.cpan/build/Device-SerialPort-1.04/t/, to be exact:
> # Allow 100ms fudge-time for slow calls, etc
> ok( ($now-$then) <= 2100, "measured sleep as less than 2 seconds")
> or diag("then: $then now: $now diff: ".($now-$then)); # test
Change that to "100ms" and "<= 2200" and it goes ahead and installs.
Can't think of a witty .sigline today....
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html