John Peacock wrote in reply to me:
!I had dozens of failures as well the testing itself failing to complete.
I
!wound up running out of diskspace while trying to build a second copy, so
I
!deleted all of the files from the earlier run (include the failed test
logs).
!I'm going to start from scratch and do both a rooted logical build as well
as
!one without a rooted logical (somewhere closer to the base of the
filesystem).
OK. I'd like to hear what happens. Thanks.
!> One other thing to note is that the PERL_SETUP.COM that
!> gets written out by CONFIGURE.COM will, if you ran
!> configure with the default of C<@configure "-des">
!> set up a definition for PERL_ROOT that does not
!> point to your source directory.
!
!I have always edited the configure.com, since it never corresponds to
where I
!will eventually install Perl anyways. Since I have always built in my
home
!directory, but installed on another drive, the generated file is never
correct.
! Perhaps it would be best to document exactly what commandline parameter
needs
!to be passed to Configure in order to specify the eventual installation
!directory. I have never even used the 'mmk install' target; I have always
used
!'mmk clean' then used backup to copy the files over to their new home.
Interesting. For what it is worth just prior to running 'mmk install'
it should still be possible to edit perl_setup.com should your desires
for relocating the installation hit you at that moment. It should
not be necessary to edit configure.com but I can see why you would want
to.
For what it is worth the manner in which one would specify a
non default location has been written to be as analogous to the Unix
process as we can get. Hence suppose that on Unix you ran:
sh Configure -Dprefix=/opt/perl/path -des
On VMS you do something similar, but you need to "" quote to
preserve case to DCL, and you need to accurately specify
a properly rooted logical name for prefix since if you
specify something wrong then configure.com assumes that
you know what you are doing (e.g. perhaps you intend to mount
the volume later):
@ Configure "-Dprefix=DKA200:[OPT.PERL.PATH.]" "-des"
(note the .] on the prefix - it becomes the PERL_ROOT rooted
logical name). That will result in 'mmk install'
putting PERL.EXE into DKA200:[OPT.PERL.PATH] and there
will be a LIB.DIR there that can be called PERL_ROOT:[LIB]
after PERL_ROOT is defined. For your information the
installperl script gets run when you invoke the install
target for MMK.
This question about how to specify "-Dprefix" has arisen on
the vmsperl list before. I think I have tended to regard it
as "already documented" in the INSTALL.;1 file but clearly
the subtleties of things like physical device name and the
.] rootedness of the prefix specification might need further
exposition. Here is what README.VMS;1 as shipped with
[EMAIL PROTECTED] has to say on the matter:
$ search readme.vms prefix/window=10
sockets, and either over no sockets). Some options can be given
explicitly on the command line; the following example specifies a
non-default location for where Perl will be installed:
@ Configure "-d" "-Dprefix=dka100:[utils.perl5.]"
Note that the installation location would be by default where you unpacked
the source with a "_ROOT." appended. For example if you unpacked the perl
source into:
***************
=item 2
Decide where you want Perl to be installed (unless you have already done so
by using the "prefix" configuration parameter -- see the example in the
"Configuring the Perl build" section).
The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM will help
you
with the definition of the PERL_ROOT and PERLSHR logical names and the PERL
foreign command symbol. Take a look at PERL_SETUP.COM and modify it if
you
Is there something about that document that
you think needs modification? Thanks.
Peter Prymmer
