+ @ Configure "-des"
+
+(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). 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:
+
+ DKA200:[PERL-5_10_2...]
+
+Then the PERL_SETUP.COM that gets written out by CONFIGURE.COM will
+try to DEFINE your installation PERL_ROOT to be:
+
+ DKA200:[PERL-5_10_2_ROOT.]
+
+More help with configure.com is available from:
+
+ @ Configure "-h"
+
+See the "Changing compile-time options (optional)" section below to learn
+even more details about how to influence the outcome of the important
+configuration step. If you find yourself reconfiguring and rebuilding
+then be sure to also follow the advice in the "Cleaning up and starting
+fresh (optional)" and the checklist of items in the "CAVEATS" sections
+below.
+
+=head2 Changing compile-time options (optional) for Perl on VMS
+
+Most of the user definable features of Perl are enabled or disabled in
+configure.com, which processes the hints file config_h.SH. There is
+code in there to Do The Right Thing, but that may end up being the
+wrong thing for you. Make sure you understand what you are doing since
+inappropriate changes to configure.com or config_h.SH can render perl
+unbuildable; odds are that there's nothing in there you'll need to
+change.
+
+=head2 Socket Support (optional) for Perl on VMS
+
+Perl includes a number of functions for IP sockets, which are available if
+you choose to compile Perl with socket support. Since IP networking is an
+optional addition to VMS, there are several different IP stacks available.
+How well integrated they are into the system depends on the stack, your
+version of VMS, and the version of your C compiler.
+
+The default solution available is to use the socket routines built into DEC
+C. Which routines are available depend on the version of VMS you're
+running, and require proper UCX emulation by your TCP/IP vendor.
+Relatively current versions of Multinet, TCPWare, Pathway, and UCX all
+provide the required libraries--check your manuals or release notes to see
+if your version is new enough.
+
+The other solution uses the SOCKETSHR library. Before VAX/VMS 5.5-2 it was
+the most portable solution. The SOCKETSHR library has not been maintained
+since VAX/VMS 5.5-2, and it is not known if will even compile with the ANSI
+C that Perl currently requires. It remains an option for historical reasons,
+just in case someone might find it useful.
+
+In combination with either UCX or NetLib, this supported all the major TCP
+stacks (Multinet, Pathways, TCPWare, UCX, and CMU) on all versions of VMS
+Perl ran on up to VAX/VMS 6.2 and Alpha VMS 1.5 with all the compilers on
+both VAX and Alpha. The portion of the socket interface was also consistent
+across versions of VMS and C compilers.
+
+It has a problem with UDP sockets when used with Multinet, though, so you
+should be aware of that.
+
+As of VAX/VMS 5.5-2 and later, CMU is the only TCP/IP program that requires
+socketshr, and the sources have been lost to the most recent CMU bug fixes,
+so CMU is limited to OpenVMS/VAX 6.2 or earlier, which is the last release
+that binaries for the last released patches are known to exist.
+
+There is currently no official web site for downloading either CMU or
+SOCKETSHR; however, copies may be found in the DECUS archives.
+
+=head1 Building Perl