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

I'm trying to build a (non-threaded) perl in a Cygwin environment.

almut here guided me through some compilation issues (Thank you!), and everything seemed to compile properly, but make test failed:

Failed Test Stat Wstat Total Fail List of Failed ---------------------------------------------------------------------- +--------- ../ext/IPC/SysV/t/ipcsysv.t 1 256 17 34 1-17 ../ext/IPC/SysV/t/msg.t 0 12 ?? ?? ?? ../ext/IPC/SysV/t/sem.t 0 12 ?? ?? ?? ../ext/Sys/Syslog/t/syslog.t 1 256 199 1 176 ../ext/Time/HiRes/t/HiRes.t 0 15 38 0 ?? op/taint.t 0 12 267 236 150-267 76 tests and 853 subtests skipped. Failed 6/1482 test scripts. 136/188699 subtests failed. Files=1482, Tests=188699, 1246 wallclock secs (343.98 cusr + 256.92 cs +ys = 600.89 CPU) Failed 6/1482 test programs. 136/188699 subtests failed.

Any and all ideas welcome...

Replies are listed 'Best First'.
Re: Cygwin Perl install - make test failed
by jettero (Monsignor) on May 28, 2009 at 21:19 UTC
    If those are all the tests that failed, that's pretty damn good. IPC and particularly syslogs aren't going to work quite right on win32... no biggie. I'm a little surprised that stuff isn't handled a little more cross-platformy; but, I mean, you are working through two layers here... there's the win32 platform itself, which differs from how perl's IPC originally expected IPC to work (c'mon, it's unix centric) and then there's cygwin, which pretends to your programs it's unix, but isn't really.

    Anyway, if those are all the tests that actually failed, I'd just install.

    UPDATE: wow! a sysv-ipc system service?!? cool. (see below)

    -Paul

      Thank you.

      That was my gut feeling, but my experience level warrants a sanity check to make sure that I'm not ignoring something important.

      Thanks again...

Re: Cygwin Perl install - make test failed
by Anonymous Monk on May 28, 2009 at 21:19 UTC
    Which perl?
      5.10.0