ftp://ftp.lp.se/vms/
http://www.openvms.compaq.com/freeware/
+Recent versions of VMS tar on ODS-5 volumes may extract tape archive
+files with ^. escaped periods in them. See below for further workarounds.
+
=item 3 UNZIP.EXE for VMS
A combination decompressor and archive reader/writer for *.zip files.
DEC C, or socket libraries. See the "Socket Support (optional)" topic
for more details.
+=head1 Unpacking the Perl source code
+
+You may need to set up a foreign symbol for the unpacking utility of choice.
+
+If you unpack a perl source kit with a name containing multiple periods on
+an ODS-5 volume using recent versions of vmstar (e.g. V3.4 or later) you may
+need to be especially careful in unpacking the tape archive file. Try to use
+the ODS-2 compatability qualifiers such as:
+
+ vmstar /extract/verbose/ods2 perl-V^.VIII^.III.tar
+
+or:
+
+ vmstar -xvof perl-5^.8^.3.tar
+
+If you neglected to use the /ODS2 qualifier or the -o switch then you
+could rename the source directory:
+
+ set security/protection=(o:rwed) perl-5^.8^.3.dir
+ rename perl-5^.8^.3.dir perl-5_8_3.dir
+
+Perl on VMS as of 5.8.3 does not completely handle extended file
+parse styles such as are encountered on ODS-5. While it can be built,
+installed, and run on ODS-5 filesystems; it may encounter
+trouble with characters that are otherwise illegal on ODS-2
+volumes (notably the ^. escaped period sequence).
+
=head1 Configuring the Perl build
To configure perl (a necessary first step), issue the command
otherwise simply deassign the dangerous logical names. The potentially
troublesome logicals and symbols are:
- TMP "LOGICAL"
- LIB "LOGICAL"
- T "LOGICAL"
- FOO "LOGICAL"
- EXT "LOGICAL"
- TEST "SYMBOL"
+ COMP "LOGICAL"
+ EXT "LOGICAL"
+ FOO "LOGICAL"
+ LIB "LOGICAL"
+ LIST "LOGICAL"
+ MIME "LOGICAL"
+ POSIX "LOGICAL"
+ SYS "LOGICAL"
+ T "LOGICAL"
+ THREAD "LOGICAL"
+ THREADS "LOGICAL"
+ TIME "LOGICAL"
+ TMP "LOGICAL"
+ UNICODE "LOGICAL"
+ UTIL "LOGICAL"
+ TEST "SYMBOL"
As a handy shortcut, the command:
At the end of all the tests, a summary of the tests, the number passed and
failed, and the time taken will be displayed.
+The test driver invoked via MMS TEST has a DCL wrapper ([.VMS]TEST.COM) that
+downgrades privileges to NETMBX, TMPMBX for the duration of the test run,
+and then restores them to their prior state upon completion of testing.
+This is done to ensure that the tests run in a private sandbox and can do no
+harm to your system even in the unlikely event something goes badly wrong in
+one of the test scripts while running the tests from a privileged account.
+A side effect of this safety precaution is that the account used to run the
+test suite must be the owner of the directory tree in which Perl has been
+built; otherwise the manipulations of temporary files and directories
+attempted by some of the tests will fail.
+
If any tests fail, it means something is wrong with Perl. If the test suite
hangs (some tests can take upwards of two or three minutes, or more if
you're on an especially slow machine, depending on your machine speed, so
where ".typ" is the file type of the Perl images you just built (if you
didn't do anything special, use .EXE), and "[.subdir]test.T" is the test
that failed. For example, with a normal Perl build, if the test indicated
-that [.op]time failed, then you'd do this:
+that t/op/time failed, then you'd do this:
@ [.VMS]TEST .EXE "" "-v" [.OP]TIME.T
+Note that test names are reported in UNIX syntax and relative to the
+top-level build directory. When supplying them individually to the test
+driver, you can use either UNIX or VMS syntax, but you must give the path
+relative to the [.T] directory and you must also add the .T extension to the
+filename. So, for example if the test lib/Math/Trig fails, you would run:
+
+ @ [.VMS]TEST .EXE "" -"v" [-.lib.math]trig.t
+
When you send in a bug report for failed tests, please include the output
from this command, which is run from the main source directory:
a VAX or on Alpha versions of VMS prior to 7.2). But MakeMaker will not
warn you if you start out building a module too deep in a directory.
+As noted above ODS-5 escape sequences such as ^. can break the perl
+build. Solutions include renaming files and directories as needed or
+being careful to use the -o switch or /ODS2 qualifier with latter
+versions of the vmstar utility when unpacking perl or CPAN modules
+on ODS-5 volumes.
+
Be sure that the process that you use to build perl has a PGFLQ greater
than 100000. Be sure to have a correct local time zone to UTC offset
defined (in seconds) in the logical name SYS$TIMEZONE_DIFFERENTIAL before
Multinet TCP/IP stack. The problem was noted in Multinet 4.3A
using either Compaq C 6.5 or DEC C 6.0, and with Multinet 4.2A
using DEC C 5.2, but could easily affect other versions of Multinet.
-A representative of Process Software Inc. has acknowledged a
-bug in the Multinet version of UCX$IPC_SHR for which there is
-an ECO forthcoming. If you see one or more tests in lib/Net/hostent
-fail we recommend that you apply the Multinet ECO when it becomes
-available from:
+Process Software Inc. has acknowledged a bug in the Multinet version
+of UCX$IPC_SHR and has provided an ECO for it. The ECO is called
+UCX_LIBRARY_EMULATION-010_A044 and is available from:
http://www.multinet.process.com/eco.html
-You may determine the version of Multinet that you are running using
-the command:
+As of this writing, the ECO is only available for Multinet versions
+4.3A and later. You may determine the version of Multinet that you
+are running using the command:
multinet show /version
from the DCL command prompt.
-If you cannot wait for the ECO from Process you might try using
-Perl programming constructs such as:
+If the ECO is unavailable for your version of Multinet and you are
+unable to upgrade, you might try using Perl programming constructs
+such as:
$address = substr($gethostbyname_addr,0,4);
https://perl5.git.perl.org / perl5.git / blobdiff