Xref: utzoo comp.lang.perl:2711 comp.sys.apollo:6886
Path: utzoo!attcan!uunet!lll-winken!sun-barr!newstop!texsun!digi.lonestar.org
From: kgallagh@digi.lonestar.org (Kevin Gallagher)
Newsgroups: comp.lang.perl,comp.sys.apollo
Subject: Re: perl difficulties on Apollo
Message-ID: <1182@digi.lonestar.org>
Date: 25 Oct 90 02:21:45 GMT
References: <2724E240.153@orion.oac.uci.edu>
Sender: kgallagh@digi.lonestar.org
Followup-To: comp.lang.perl
Organization: DSC Communications, Plano Tx.
Lines: 32

In article <2724E240.153@orion.oac.uci.edu> mheffron@orion.oac.uci.edu (Matt Heffron) writes: 
>I've just installed perl V3.0 pl 37 on an Apollo DN3500 running Domain/OS (10.2) 
>and two tests fail, both with file mode related errors. Does anyone have any 
>advice/opinions/... ?  
>[examples deleted] 

I had similar problems when I first installed perl 3.0, pl 18, on a DN3500.
Here's what happened and how I fixed the problem.

I installed perl under Apollo's implementation of bsd4.3.  I too found file
mode related problems.  After several days, it dawned on me that 6 months
earlier, when our Apollo's were first installed, they installed all users
under sys5.3.  This meant that everyone's directory structures were set up
with Apollo ACL to emulate sys5 directory protections and inheritance.  Three
months later, it was decided to switch everyone to have their default
environment to be bsd4.3.  HOWEVER, they did not convert user directories to
have Apollo's emulation of bsd directory protections and inheritance!

So, since I built perl under bsd, and Configure told me that it knew I was
running bsd, I concluded that perl was built to expect a pure bsd directory
structure.  So, I went to the perl/t directory and set the acl on that
directory (and its contents) to emulate a bsd directory structure.  I used the
Apollo chacl command, using the -B option.  After that, all the file mode
related errors went away!

Last weekend I installed perl, pl 38, and had no problems.  All tests passed,
with the exception of op.sleep, which sometimes fails and sometimes passes,
because it does not always sleep for the 2 full seconds specified in the test
script.  But this is to be expected in "standard" Unix.  (Apollo is proud of
the fact that it's emulation of Unix is "just like Unix", bugs and limitations
included!)

Good luck!