From 046cc26cf77f76bc63fd4d206fef560054f5d298 Mon Sep 17 00:00:00 2001 From: "Craig A. Berry" Date: Sat, 3 Sep 2011 14:44:11 -0500 Subject: Remove sockadapt layer from the VMS build. SOCKETSHR is/was an interface to abstract out TCP/IP calls for the various vendors' networking implementations, including the freeware CMU-IP stack. Neither SOCKETSHR nor CMU-IP has seen any maintenance for over a decade and are likely not even C89-compliant. The CRTL socket routines have been supported by the different vendors' stacks for many years so there is no reason to maintain an alternative, and there probably hasn't been a real working alternative for some years anyway. The code is still there in maint-5.14 and earlier branches if anyone has need of it. --- README.vms | 44 ++++++-------------------------------------- 1 file changed, 6 insertions(+), 38 deletions(-) (limited to 'README.vms') diff --git a/README.vms b/README.vms index 8d3c8a23da..8195d6af8f 100644 --- a/README.vms +++ b/README.vms @@ -212,10 +212,9 @@ As a handy shortcut, the command: @ 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: +automatically. 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.]" @@ -254,40 +253,9 @@ 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. +you choose to compile Perl with socket support. It does this via the socket +routines built into the CRTL regarless of which TCP/IP stack your system +has. =head1 Building Perl -- cgit v1.2.1