Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!burdvax!fritzson
From: fritzson@PRC.Unisys.COM (Richard Fritzson)
Newsgroups: comp.lang.perl
Subject: Re: Porting PERL on Silicon Graphics 4D
Message-ID: <16987@burdvax.PRC.Unisys.COM>
Date: 27 Mar 91 15:37:35 GMT
References: <21225@shlump.nac.dec.com> <45819@ut-emx.uucp> <1991Mar25.195636.9974@alias.com> <1991Mar27.070646.11213@riacs.edu>
Sender: news@PRC.Unisys.COM
Organization: Unisys Corporation, Paoli Research Center; Paoli, PA
Lines: 29

In article <1991Mar27.070646.11213@riacs.edu> samlb@pioneer.arc.nasa.gov (Sam Bassett RCS) writes:
>
>	I did all of that on our IRIX 3.3.1 system, and got an
>(apparently) working perl out of it -- but the tests won't run.  If I
>type 'make test', it 'cd's to the 't' directory, moves stuff around, and
>then tells me that "No tests were run for some reason".
>	I tweaked the TEST file, and tried everything I could think of,
>and still nothing.  Anybody got any ideas?

I have run into the same problem. The only "next thing" I determined
was that  the reason for the "No tests were run for some reason"
messages is  that the backquote facility isn't working in the
constructed Perl.

Have you tried this? :

chk@alias.com  writes:

>vfork, memcmp, and volatile are all broken under IRIX3.3. To get perl to
>compile and work, you have to manually disable these three in the config.sh
>file. Do this at the end when Configure asks you if you want to edit
>config.sh.
>
>Also, you have to specify -D_BSD_COMPAT as one of the arguments to the C
>compiler (there's a question that asks for this near the beginning of
>Configure).

Rich Fritzson				             fritzson@prc.unisys.com
Unisys - Center for Advanced Information Technology  (215) 648-2972