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
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.2).
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
=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.
=item 1 GUNZIP/GZIP.EXE for VMS
A de-compressor for *.gz and *.tgz files available from a number
-of web/ftp sites.
+of web/ftp sites and is distributed on the OpenVMS Freeware CD-ROM
+from Compaq.
http://www.fsf.org/order/ftp.html
- ftp://ftp.uu.net/archive/systems/gnu/diffutils*.tar.gz
- ftp://gatekeeper.dec.com/pub/GNU/diffutils*.tar.gz
- ftp://ftp.gnu.org/pub/gnu/diffutils*.tar.gz
- http://www.openvms.digital.com/cd/GZIP/
- ftp://ftp.digital.com/pub/VMS/
+ http://www.openvms.compaq.com/freeware/GZIP/
+ ftp://ftp.compaq.com/pub/VMS/
+ http://www.crinoid.com/utils/
=item 2 VMS TAR
For reading and writing unix tape archives (*.tar files). Vmstar is also
-available from a number of web/ftp sites.
+available from a number of web/ftp sites and is distributed on the OpenVMS
+Freeware CD-ROM from Compaq.
ftp://ftp.lp.se/vms/
- http://www.openvms.digital.com/cd/VMSTAR/
- ftp://ftp.digital.com/pub/VMS/
+ http://www.openvms.compaq.com/freeware/VMSTAR/
+ ftp://ftp.compaq.com/pub/VMS/
=item 3 UNZIP.EXE for VMS
Unzip is available from a number of web/ftp sites.
http://www.cdrom.com/pub/infozip/UnZip.html
- http://www.openvms.digital.com/cd/INFO-ZIP/
- ftp://ftp.digital.com/pub/VMS/
- ftp://ftp.openvms.digital.com/
+ http://www.openvms.compaq.com/freeware/INFO-ZIP/
+ ftp://ftp.compaq.com/pub/VMS/
+ ftp://ftp.openvms.compaq.com/
ftp://ftp.madgoat.com/madgoat/
ftp://ftp.wku.edu/vms/
ftp://space.mit.edu/pub/davis/
ftp://ftp.wku.edu/vms/narnia/most.zip
+=item 5 GNU PATCH and DIFFUTILS for VMS
+
+Patches to Perl are usually distributed as GNU unified or contextual diffs.
+Such patches are created by the GNU diff program (part of the diffutils
+distribution) and applied with GNU patch. VMS ports of these utilities are
+available here:
+
+ http://www.crinoid.com/utils/
+
=back
Please note that UNZIP and GUNZIP are not the same thing (they work with
different formats). Many of the useful files from CPAN (the Comprehensive
-Perl Archive Network) are in *.tar.gz format (this includes copies of the
-source code for perl as well as modules and scripts that you may wish to
-add later) hence you probably want to have GUNZIP.EXE and VMSTAR.EXE on
-your VMS machine.
+Perl Archive Network) are in *.tar.gz or *.tgz format (this includes copies
+of the source code for perl as well as modules and scripts that you may
+wish to add later) hence you probably want to have GUNZIP.EXE and
+VMSTAR.EXE on your VMS machine.
If you want to include socket support, you'll need a TCP/IP stack and either
DEC C, or socket libraries. See the "Socket Support (optional)" topic
(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"
There are several steps you need to take to get Perl installed and
running.
-1) Create a directory somewhere and define the concealed logical PERL_ROOT
-to point to it. For example,
+=over 4
- CREATE/DIRECTORY dka200:[perl]
- DEFINE/TRANS=(CONC,TERM) PERL_ROOT dka200:[perl.]
+=item 1
-2) Run the install script via:
+Check your default file protections with
- MMS install
+ SHOW PROTECTION /DEFAULT
-or
+and adjust if necessary with SET PROTECTION=(code)/DEFAULT.
- MMK install
+=item 2
-If for some reason it complains about target INSTALL being up to date,
-throw a /FORCE switch on the MMS or MMK command.
+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 [.VMS]PERL_SETUP.COM that is written by CONFIGURE.COM
-will take care of most of the following:
+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
+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.
-3) Either create the global foreign symbol PERL somewhere, such as
-SYS$MANAGER:SYLOGIN.COM, to be
+=item 3
- $ PERL :== "$PERL_ROOT:[000000]PERL.EXE"
+Run the install script via:
-or install Perl into DCLTABLES.EXE (Check out the section "Installing Perl
-into DCLTABLES (optional)" for more information), or put the image in a
-directory that's in your DCL$PATH (if you're using VMS V6.2 or higher).
+ MMS install
-4) Either define the logical name PERLSHR somewhere
-(such as in PERL_SETUP.COM) like so
+or
- $ DEFINE/NOLOG PERLSHR PERL_ROOT:[000000]PERLSHR.EXE
+ MMK install
-or copy the file into the system shareable library directory with
+If for some reason it complains about target INSTALL being up to date,
+throw a /FORCE switch on the MMS or MMK command.
- copy perl_root:[000000]perlshr.exe sys$share:
+=back
-5) Optionally define the command PERLDOC as
+Copy PERL_SETUP.COM to a place accessible to your perl users.
- $ PERLDOC == "$PERL_ROOT:[000000]PERL PERL_ROOT:[LIB.POD]PERLDOC.COM -t"
+For example:
-(See above for where to find the B<most> pager for use with perldoc).
+ COPY PERL_SETUP.COM SYS$LIBRARY:
-6) Optionally define the command PERLBUG (the Perl bug report generator) as
+If you want to have everyone on the system have access to perl
+then add a line that reads
- $ PERLBUG == "$PERL_ROOT:[000000]PERL PERL_ROOT:[LIB]PERLBUG.COM"
+ $ @sys$library:perl_setup
-7) Optionally define the command POD2MAN (Converts POD files to nroff
-source suitable for converting to man pages. Also quiets complaints during
-module builds) as
+to SYS$MANAGER:SYLOGIN.COM.
- $ DEFINE/NOLOG POD2MAN PERL_ROOT:[LIB.POD]POD2MAN.COM
- $ POD2MAN == "$PERL_ROOT:[000000]PERL POD2MAN"
+Two alternatives to the foreign symbol would be to install PERL into
+DCLTABLES.EXE (Check out the section "Installing Perl into DCLTABLES
+(optional)" for more information), or put the image in a
+directory that's in your DCL$PATH (if you're using VMS V6.2 or higher).
-8) Optionally define the command POD2TEXT (Converts POD files to text,
-which is required for B<perldoc -f> to work properly) as
+An alternative to having PERL_SETUP.COM define the PERLSHR logical name
+is to simply copy it into the system shareable library directory with:
- $ DEFINE/NOLOG POD2TEXT PERL_ROOT:[LIB.POD]POD2TEXT.COM
- $ POD2TEXT == "$PERL_ROOT:[000000]PERL POD2TEXT"
+ copy perl_root:[000000]perlshr.exe sys$share:
-In all these cases, if you've got PERL defined as a foreign command symbol,
-you can replace $PERL_ROOT:[000000]PERL with ''perl'. If you have installed
-perl into DCLTABLES, replace it with just perl.
+See also the "INSTALLing images (optional)" section.
=head2 Installing Perl into DCLTABLES (optional)
On systems that are using perl quite a bit, and particularly those with
minimal RAM, you can boost the performance of perl by INSTALLing it as
-a known image. PERLSHR.EXE is typically larger than 2000 blocks
+a known image. PERLSHR.EXE is typically larger than 2500 blocks
and that is a reasonably large amount of IO to load each time perl is
invoked.
Perl exited. This is fixed by DEC CSC patch ALPACRT04_061 or later.
See also:
- http://ftp.service.digital.com/patches/.new/openvms.html
+ http://ftp.service.compaq.com/patches/.new/openvms.html
=back
there is the VMSPERL mailing list. It is usually a low-volume (10-12
messages a week) mailing list.
-The subscription address is MAJORDOMO@PERL.ORG. Send a mail message with
-just the words SUBSCRIBE VMSPERL in the body of the message.
-
-The VMSPERL mailing list address is VMSPERL@PERL.ORG. Any mail sent there
-gets echoed to all subscribers of the list. There is a searchable archive of
-the list on the web at:
+To subscribe, send a mail message to VMSPERL-SUBSCRIBE@PERL.ORG. The VMSPERL
+mailing list address is VMSPERL@PERL.ORG. Any mail sent there gets echoed
+to all subscribers of the list. There is a searchable archive of the list
+on the web at:
http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
-To unsubscribe from VMSPERL send the message UNSUBSCRIBE VMSPERL to
-MAJORDOMO@PERL.ORG. Be sure to do so from the subscribed account that
-you are canceling.
+To unsubscribe from VMSPERL send a message to VMSPERL-UNSUBSCRIBE@PERL.ORG.
+Be sure to do so from the subscribed account that you are canceling.
=head2 Web sites
Vmsperl pages on the web include:
http://www.sidhe.org/vmsperl/index.html
+ http://www.crinoid.com/
http://duphy4.physics.drexel.edu/pub/cgi_info.htmlx
- http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
http://www.cpan.org/modules/by-module/VMS/
+ http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/
http://nucwww.chem.sunysb.edu/htbin/software_list.cgi
http://www.best.com/~pvhp/vms/
http://bkfug.kfunigraz.ac.at/~binder/perl.html
+ http://lists.perl.org/showlist.cgi?name=vmsperl
+ http://archive.develooper.com/vmsperl@perl.org/
=head1 SEE ALSO
=head1 AUTHORS
-Last revised 13-February-2000 by Peter Prymmer pvhp@best.com.
-Revised 27-October-1999 by Craig Berry craig.berry@metamorgs.com.
+Revised 5-April-2001 by Craig Berry craigberry@mac.com.
+Revised 25-February-2000 by Peter Prymmer pvhp@best.com.
+Revised 27-October-1999 by Craig Berry craigberry@mac.com.
Revised 01-March-1999 by Dan Sugalski dan@sidhe.org.
Originally by Charles Bailey bailey@newman.upenn.edu.
the Stanford Synchrotron Radiation Laboratory and the
Laboratory of Nuclear Studies at Cornell University for
the opportunity to test and develop for the AXP,
+ John Hasstedt John.Hasstedt@sunysb.edu
+ for VAX VMS V7.2 support
and to the entire VMSperl group for useful advice and suggestions. In
addition the perl5-porters deserve credit for their creativity and
https://perl5.git.perl.org / perl5.git / blobdiff