> And it would really help to know which one you're following 

Yeah, I know, but after a couple of days it's a little blurry as to what
problem was noticed from which set of docs.  It hasn't helped that this has
been a moving target, make one failure go away and another shows up
somewhere else.  Had it been a consistent failure, it'd be a lot easier to
point a finger and say Ah Ha!

> I don't know if the patch sets from www.crinoid.com

Nope, I hadn't come across this site yet.  Basically, I've been following
the link from www.perl.org to various VMS sites looking for tid bits as to
what goes where and in what order.

> Weird, never saw that one before.
> > [.pod]pod2usage.........FAILED on test 1 (hangs at this point)

This started after moving the install directory to a subdirectory off of the
root directory.  I even deleted everything and reinstalled a fresh
downloaded copy and can still reproduce the error.

> > Should l see any test failures?
> No, it *is* possible to get a clean build/test.

Possible?  So this is to say that I should not expect the base 5.6 to be a
clean install?

> > Is there a concise set of instructions for 
> http://www.crinoid.com/

Um, I found instructions for applying patches, I didn't see anything about
actually getting a clean install of PERL though.  Or were you implying that
I should attempt to apply the patches and rerun the MMK TEST?

> > Should the PERL_ROOT: logical point to a directory at the root level?
> It can be one or two levels down. What I generally do is something like
>    $ define/trans=conceal xroot disk:[perl.perl560.]
>    $ set default xroot:[000000]
>    $ mmk

With the following (copied from my sylogicals):

$ dsr   := define/system/executive/translation=(CONCEALED,TERMINAL)
<snip>
$ dsr   perl_root               DRA0:[SYS0.SYSCOMMON.perl.]

I was able to run a MMK TEST that while it still had failures, did not hang.
Unfortunately, the MMK INSTALL failed at that point which is what led to the
question about moving the [.LIB] directory with a rename.

> Ah, but the *next* program will be a lot faster! :)

At the rate I'm going, there won't be a next program! :-)

The PERL installation at this point seems to run, or at least I haven't
exercised anything that causes a fatal error other than trying to use and
understand how the VMS interface works.  Lacking the VMS interface, I'm
going to try to use PERL to build .com files that I can run to accomplish
what I need for now.

Thanks,
Mike Benedict

Reply via email to