X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.vms;h=d9ea97ea52e81de96144e3f83f8485e1a3f14da3;hb=2decb4fb82e001e3c9671c57b61232c651a9c22c;hp=13a1f9bb51ada7c0cc74aa1f06aeb67faa92ab13;hpb=1d7c184104c076988718a01b77c8706aae05b092;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/README.vms b/README.vms
index 13a1f9b..d9ea97e 100644
--- a/README.vms
+++ b/README.vms
@@ -6,7 +6,7 @@ Originally by Charles Bailey <bailey@newman.upenn.edu>
 
 The build and install procedures have changed significantly from the 5.004
 releases! Make sure you read the "Building Perl" and "Installing Perl"
-sections before you build or install.
+sections of this document before you build or install.
 
 Also note that, as of 5.005, an ANSI C compliant compiler is required to
 build Perl. Vax C is *not* ANSI compliant, as it died a natural death some
@@ -84,7 +84,7 @@ Building perl has two steps, configuration and compilation.
 
 To configure perl (a necessary first step), issue the command
 
-@CONFIGURE
+   @CONFIGURE
 
 from the top of an unpacked perl directory. You'll be asked a series of
 questions, and the answers to them (along with the capabilities of your C
@@ -96,7 +96,22 @@ you're using a version older than 5.2, check the Dec C Issues section.
 
 The configuration script will print out, at the very end, the MMS or MMK
 command you need to compile perl. Issue it (exactly as printed) to start
-the build.
+the build.  If you have any symbols or logical names in your environment
+that may interfere with the build or regression testing of perl then 
+configure.com will try to warn you about them.  If a logical name is causing
+you trouble but is in an LNM table that you do not have write access to
+then try defining your own to a harmless equivalence string in a table 
+such that it is resolved before the other (e.g. if TMP is defined in the
+SYSTEM table then try DEFINE TMP "NL:" or somesuch) otherwise simply deasign 
+the dangerous logical names.  The potentially troublesome logicals and
+symbols are:
+
+    TMP  "LOGICAL"
+    LIB  "LOGICAL"
+    T    "LOGICAL"
+    FOO  "LOGICAL"
+    EXT  "LOGICAL"
+    TEST "SYMBOL"
 
 Once you issue your MMS command, sit back and wait. Perl should build and
 link without a problem. If it doesn't, check the Gotchas to watch out for
@@ -105,7 +120,7 @@ Instructions are in the Mailing Lists section.
 
 As a handy shortcut, the command:
 
-@CONFIGURE "-des"
+    @CONFIGURE "-des"
 
 (note the quotation marks and case) will choose reasonable defaults. (It 
 takes Dec C over Gnu C, Dec C sockets over SOCKETSHR sockets, and either 
@@ -245,18 +260,18 @@ into DCLTABLES, replace it with just perl.
 Execute the following command file to define PERL as a DCL command.
 You'll need CMKRNL priv to install the new dcltables.exe.
 
-$ create perl.cld
-!
-! modify to reflect location of your perl.exe
-!
-define verb perl
-  image perl_root:[000000]perl.exe
-  cliflags (foreign)
-$!
-$ set command perl /table=sys$common:[syslib]dcltables.exe -
- /output=sys$common:[syslib]dcltables.exe
-$ install replace sys$common:[syslib]dcltables.exe
-$ exit
+    $ create perl.cld
+    !
+    ! modify to reflect location of your perl.exe
+    !
+    define verb perl
+      image perl_root:[000000]perl.exe
+      cliflags (foreign)
+    $!
+    $ set command perl /table=sys$common:[syslib]dcltables.exe -
+     /output=sys$common:[syslib]dcltables.exe
+    $ install replace sys$common:[syslib]dcltables.exe
+    $ exit
 
 * Changing compile-time things
 
@@ -410,7 +425,7 @@ missed someone.  That said, special thanks are due to the following:
      for the getredirection() code
   Rich Salz <rsalz@bbn.com>
      for readdir() and related routines
-  Peter Prymmer <pvhp@forte.com> or <pvhp@lns62.lns.cornell.edu>
+  Peter Prymmer <pvhp@forte.com> 
      for extensive testing, as well as development work on
      configuration and documentation for VMS Perl,
   Dan Sugalski <dan@sidhe.org>