Looks good.
On Thu, 5 Apr 2001, Craig A. Berry wrote:
> At 04:16 PM 4/3/2001 -0700, Peter Prymmer wrote:
>
> >> > Perhaps too we ought to give an example of a
> >> >_proper_ prefix setting in README.vms?
> >>
> >> Yes, yes :-).
> >
> >Do you want to take a crack at it? I have to document UTF-EBCDIC for
> >OS/390 aka z/OS...(plus oodles of day job stuff).
>
> I've started to take a look at this and discovered that we don't need to create any
>directories for the installation since the install target will do that for you.
>Also, telling people to set perl_root before the installation is downright misleading
>since the installation now unilaterally uses whatever is in perl_setup.com. Let me
>know if this sounds reasonable. If we have a prayer of getting it into 5.6.1 we need
>to send it in soon:
> --- readme.vms;-0 Thu Feb 22 20:57:53 2001
> +++ readme.vms Wed Apr 4 17:40:49 2001
> @@ -29,7 +29,7 @@
> Also note that, as of Perl version 5.005 and later, an ANSI C compliant
> compiler is required to build Perl. VAX C is *not* ANSI compliant, as it
> died a natural death some time before the standard was set. Therefore
> -VAX C will not compile perl 5.005. We are sorry about that.
> +VAX C will not compile perl 5.005 or later. We are sorry about that.
>
> If you are stuck without DEC C (the VAX C license should be good for DEC C,
> but the media charges might prohibit an upgrade), consider getting Gnu C
> @@ -52,7 +52,8 @@
>
> The current sources and build procedures have been tested on a VAX using
> DEC C, and on an AXP using DEC C. If you run into problems with
> -other compilers, please let us know.
> +other compilers, please let us know. (Note: DEC C was renamed to Compaq C
> +around version 6.0).
^^^
Perhaps that ought to read:
> +around version 6.2).
N.B.:
$ cc/version nl:
DEC C V5.3-006 on OpenVMS VAX V6.2
$ cc/version nl:
DEC C V5.5-002 on OpenVMS Alpha V7.1
$ cc/version nl:
DEC C V6.0-001 on OpenVMS Alpha V7.1
$ cc/version nl:
Compaq C V6.2-008 on OpenVMS Alpha V7.1
$ cc/version nl:
Compaq C V6.4-005 on OpenVMS Alpha V7.2-1
> There are issues with various versions of DEC C, so if you're not running a
> relatively modern version, check the "DEC C issues" section later on in this
> @@ -66,7 +67,7 @@
>
> =item 1 A C compiler.
>
> -DEC C or gcc for VMS (AXP or VAX).
> +DEC (now Compaq) C or gcc for VMS (AXP or VAX).
>
> =item 2 A make tool.
>
> @@ -180,8 +181,13 @@
>
> (note the quotation marks and case) will choose reasonable defaults
> automatically (it takes DEC C over Gnu C, DEC C sockets over SOCKETSHR
> -sockets, and either over no sockets). More help with configure.com is
> -available from:
> +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.]"
> +
> +More help with configure.com is available from:
>
> @ Configure "-h"
>
> @@ -341,19 +347,13 @@
>
> =item 2
>
> -Create a directory somewhere and either run @perl_setup or
> -define the concealed logical PERL_ROOT to point to it by hand.
> -For example,
> -
> - CREATE/DIRECTORY dka200:[perl]
> - @PERL_SETUP
> - SHOW LOGICAL PERL_ROOT
> -
> -or,
> -
> - CREATE/DIRECTORY dka200:[perl]
> - DEFINE/TRANS=(CONC,TERM) PERL_ROOT dka200:[perl.]
> -
> +The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM will help
> +you with the definition of PERL_ROOT, PERLSHR and the PERL Foreign
> +symbol. Take a look at PERL_SETUP.COM and modify it if you want to.
> +The installation process will execute PERL_SETUP.COM and copy files to
> +the directory tree pointed to by the PERL_ROOT logical name defined
> +there, so make sure that you have write access to the parent directory
> +of what will become the root of your Perl installation.
>
> =item 3
>
> @@ -370,10 +370,8 @@
>
> =back
>
> -The DCL script PERL_SETUP.COM that is written by CONFIGURE.COM
> -will help you with the definition of PERL_ROOT, PERLSHR and the PERL
> -Foreign symbol. Take a look at PERL_SETUP.COM and modify it if you want
> -to. Then copy PERL_SETUP.COM to a place accessible to your perl users.
> +Copy PERL_SETUP.COM to a place accessible to your perl users.
> +
> For example:
>
> COPY PERL_SETUP.COM SYS$LIBRARY:
Looks good. Thank you. Perhaps not in time for 5.6.1 but I think we
should do a:
$ search configure.com "f$type("
and figure out and document which config vars configure.com knows about
apart from prefix. Note too that if you set a symbol as in (note that
local symbols will work, the assignment need not be == global):
$ prefix := DKA200:[MYPERL.]
$ @configure "-des"
then perl_setup.com will have a
C<$ define perl_root/trans=conc DKA200:[MYPERL.]> type statement in it as
well (i.e. it is not _necessary_ to use "-Dprefix=DKA200:[MYPERL.]",
but it would be helpful to list which symbols are checked and
pre-settable before the run of @configure.com).
Peter Prymmer
