This distribution contains everything you need to install gcc 2.3.3, g++ 2.3.3 and/or libg++ 2.3 on a VMS system (previous versions of the distribution at mango were only contained compiler executables, and you had to load the gcc-vms distribution from prep.ai.mit.edu). The only prerequisite is a running VMS system (version 5.n), and sufficient disk space. Once gcc 2.n is out of beta testing, then the gcc-vms distribution on prep will be updated to contain the 2.n executables. The gcc 2.3.3/g++ 2.3.3 compilers and the libg++ distribution are all in compressed save sets that can be installed with VMSINSTAL. All you need to do is to pick up the parts you need, decompress them, and run VMSINSTAL. The kit parts are: gcc023.a_z Required. Only contains kitinstal.com, so that we get a fast startup with VMSINSTAL. gcc023.b_z gcc 2.3.3 compiler, preprocessor, header files compiler driver, and assorted goodies. gcc023.c_z bison gcc023.d_z g++ 2.3.3 compiler gcc023.e_z libg++ 2.3 distribution. gcc023.f_z Info files. For example, if you wanted gcc 2.3.3 and g++ 2.3.3, but were not interested in libg++ or bison, you would need parts a, b, d and f. The approximate disk space requirements are: Component To install Final --------- ---------- ----- gcc 4600 4000 bison 320 320 g++ 2600 2600 libg++ 5200 2850 info 1950 1950 ----- ----- ----- Total 14670 11720 When you run VMSINSTAL, simply give the name of the directory that contains the decompressed kit parts as the location of the product. Give "gcc023" as the name of the product to be installed. If you are short on disk space, you can copy the decompressed save-sets to magnetic tape with A being first and continuing on in alphabetical order, and then installing from tape. This will be slower. You do not have to throw any users off the system to install gcc, but they will not get the updated command tables until they have logged out and then back in again. The files should be decompressed on a VMS system, because there is information stored in the ldcmp header that describes the file type. For information regarding the VMSINSTAL utility, see the manual "Guide to VAX/VMS Software Installation". You can also (from a privileged account) type "@SYS$UPDATE:VMSINSTAL", and then enter a '?' whenever you are prompted in order to get more information. If you do not have a privileged account available, you can use the following command procedure, which will also perform the installation. This uses the same command procedure that you would use if you were using the system VMSINSTAL, but it is not as smart. If you have access to the privileged account it is probably safer to use the VMSINSTAL in sys$update. $! $! A *very* limited version of VMSINSTAL that works from a non-privileged $! account $! $flnm = f$enviroment("PROCEDURE") ! get current procedure name $defloc = f$parse(flnm,,,"DEVICE")+f$parse(flnm,,,"DIRECTORY") $set default 'f$parse(flnm,,,"DEVICE")''f$parse(flnm,,,"DIRECTORY")' $! $say := write sys$output $ say "This version of VMSINSTAL is much more limited than the" $ say "One that comes with a VMS system. If you have system" $ say "privileges, it would be best to use the one in sys$update." $! $ say "" $ inquire dloc "Where can the distribution be found?" $ inquire product "Product" $ assign 'dloc' vmi$dist $say "" $say " Beginning installation of ''product' at ",f$time() $ backup vmi$dist:'product'.A/save *.*/nolog $! $@kitinstal $! $flnm = f$enviroment("PROCEDURE") ! get current procedure name $defloc = f$parse(flnm,,,"DEVICE")+f$parse(flnm,,,"DIRECTORY") $set default 'f$parse(flnm,,,"DEVICE")''f$parse(flnm,,,"DIRECTORY")' $delete/nolog kitinstal.com; $say " Completing installation of ''product' at ",f$time()