A    A new version of the BLISS-32 compiler is now available.  This F    version, BLISS-32 V4.7-999, includes new features for compatibility     with MIPS and Alpha dialects.  (                                     NOTE  9            The format of BLISS library files has changed. ?            Library files compiled with this version of BLISS-32 >            cannot be used with prior versions of the compiler,?            but old library files can be used with this version.           4                         HOW TO INSTALL BLISS-32 V4.7    <    This describes the installation procedures for the VAX-117    Bliss-32 Version 4.7 compiler.  You should read this 0    completely before beginning the installation.          4.1  INSTALLATION PROCEDURE  +    To install Bliss-32, proceed as follows:   H    1.  Log in under the privileged system manager's account.  Since thisH        installation procedure will recompile STARLET.REQ and LIB.REQ (ifI        present in [SYSLIB]), this account should have a large working-set B        limit (500 to 1000 pages is recommended) to insure that the%        installation proceeds quickly.           Issue the command:   9        $ @SYS$UPDATE:VMSINSTAL BLS32047 <location of kit>   F        (To install in a system root other than the root of the running=        system, you can use the following alternative command:   J        $ @SYS$UPDATE:VMSINSTAL BLS32047 <location of kit> OPTIONS R <root>  E        where <root> specifies the alternate system root in the format         "__ddcu:[SYSn.]".)   *                                       NOTE  @                You should have at least 5000 free blocks on your6                system disk device before beginning the&                installation procedure.      A    2.  If there are other users on the system, or you have DECnet G        running, VMSINSTAL will warn you and ask if you want to continue H        with the installation.  DECnet should not cause any problems.  ItI        is slightly safer to install when you have the system to yourself, F        but other users on the system normally will not cause problems.  F        VMSINSTAL will also ask if you are satisfied with the backup ofD        your system disk.  It is always a good idea to have a currentG        system disk backup before performing an installation.  VMSINSTAL         will then report:    ,    The following products will be processed:        BLS32 V4.7     8            Beginning installation of BLS32 V4.7 at hh:mm  9    %VMSINSTAL-I-RESTORE, Restoring product save set A ... N    %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  1                                     BLISS-32 V4.7     Q      Copyright  Digital Equipment Corporation. 1976, 1993.  All rights reserved.                        Product:      BLISS32            Producer:     DEC            Version:      4.7#            Release Date: 3-OCT-1989     G    * Does this product have an authorization key registered and loaded?   2    If you respond "NO" the installation continues:  K    %BLS32-W-NOLICENSE, License not registered.  Installation will continue.   C                    After your BLISS-32 license has been registered, D                    compile the system require files and run the IVP.  7                    To compile the system require files:   4                            $ SET DEFAULT SYS$LIBRARY2                            $ BLISS/LIBRARY STARLET:                            $ BLISS/LIBRARY=LIB STARLET+LIB1                            $ BLISS/LIBRARY TPAMAC   "                    To run the IVP:  2                            $ @SYS$TEST:BLISS32$IVP          The installation continues:  9    %VMSINSTAL-I-RESTORE, Restoring product save set B ...   D    * Do you want to purge files replaced by this installation [YES]?=    * Do you want to run the IVP after the installation [YES]?   L            This kit contains a  file  summarizing the new features, changes,L            restrictions,  and  compatibility issues  in this release of  VAXL            BLISS-32.  This file is named  BLS32047.RELEASE_NOTES and will be            placed in SYS$HELP:.   L            The  release notes  contains information valuable to VAX BLISS-32L            programmers.   Please  inform  your  VAX  BLISS-32  users of this            file's existence.  L            The BLISS help file contains extensive documentation on the BLISSL            language.  Since this material  requires about 525 blocks of disk,            space, its inclusion is optional.  *    * Do you want the long help file [YES]?  H            All questions regarding the installation have now been asked.6            The system directories will now be updated.  8    %BLS32-I-LIBBUILD, Building the precompiled libraries  L            This phase of the installation process compiles the STARLET, LIB,L            and TPAMAC L32 files.  The corresponding REQ  files  are expectedL            to  be  in  SYS$LIBRARY.   If one is missing,  you will receive aL            warning message and that library file will not be created.   This@            will not interfere with the rest of the installation.  B    %VMSINSTAL-I-SYSDIR, This product creates system disk directory      VMI$ROOT:[SYSTEST.BLS32].  4            * * * * * * * * * * * * * * * * * * * * *4            *                                       *4            *   This kit and its contents are for   *4            *                                       *4            *       DIGITAL INTERNAL USE ONLY.      *4            *                                       *4            * * * * * * * * * * * * * * * * * * * * *    Q    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...   ?    If you said that the PAK had been installed, the IVP is run:   ?    %BLS32-I-IVP, Performing Installation Verification Procedure     #         *************************** !           Successful Installation                      of             VAX Bliss-32 V4.7-999#         ***************************       8            Installation of BLS32 V4.7 completed at hh:mm    ,            VMSINSTAL procedure done at hh:mm  G    3.  If BLISS32 is a known shared image on your system, you will have >        to use the INSTALL utility to replace it at this point.