At 10:20 AM -0600 10/29/00, Mike Benedict wrote:
>
>> 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.
The OpenVMS FAQ off of www.openvms.compaq.com has an up-to-date Perl
section, but some other sites -- including, I think, perl.org -- are
rather behind. Sorry about that. There's always room for one more
overworked volunteer if you'd like to help us chase down details like
this :-).
> > 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.
I lost you here. You were getting test failures running the test
suite *after* a failed MMK INSTALL? As far as I know, the test suite
is only designed to work in the build tree before installation.
> > > 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?
Unfortunately not. We have high hopes for 5.6.1, but that's still
weeks or perhaps months away.
> > > 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?
Before applying the patches (from crinoid or the consolidated one I
posted a pointer to earlier), your best bet would be to start from
scratch with a freshly unpacked tarball, apply the patches,
configure, build, test, and install. The patches are unlikely to do
any good on a kit that has already been configured, much less built
and tested. This presupposes a working copy of GNU patch, which can
also be difficult to come by. The version here should work (a better
one is under development):
<ftp://ftp.sidhe.org/VMSPerl_Community/non-perl_utils/patch-2_5_4-vms.zip>
>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.
What do you mean by "the VMS interface"? the callable mail
interface? Again, MIME::Lite (the easiest) or Net::SMTP (more
control) would be the more Perl-like ways to do this, although Perl
wrappers to command files is certainly doable as well. If you mean
how to access DCL from Perl, there is, as usual, more than one way to
do it, but here's a simple example:
$ perl -e "system(qw/write sys$output ""hello""/);"
hello
--
____________________________________________
Craig A. Berry
mailto:[EMAIL PROTECTED]
