Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!gatech!mcnc!uvaarpa!mmdf
From: marc@athena.mit.edu
Newsgroups: comp.lang.perl
Subject: Ultrix 3.1
Message-ID: <1990Oct25.041755.16345@uvaarpa.Virginia.EDU>
Date: 25 Oct 90 04:17:55 GMT
Sender: mmdf@uvaarpa.Virginia.EDU (Uvaarpa Mail System)
Reply-To: marc@mit.edu
Organization: The Internet
Lines: 26

We're running a slightly hacked ultrix 3.1 here, and when I built
pl37, I ran into problems with op.exec test 4 failing.  The problem
seemed to be with waitpid() never changing its argument to reflect the
status of the program which exited.  I don't know where waitpid()
comes from, but it may be the source of op.exec 4 losing on other
machines.  The workaround is to edit config.sh to undef d_waitpid.
Ultrix 4.0 doesn't seem to have this problem, from what I've been
observing on this list.

There also seems to be a bug in the test stuff.  The test script, when
run individually, printed 

    1..8
    ok 1
    not ok 1
    ok 2
    not ok 2
    ok 3
    not ok 3
    not ok 4

t/TEST claimed test 4 failed.  This is certainly true, but tests 1,2,3
failed, too, and the test script didn't seem to notice.  This is pl37
also.

		Marc