DataMuseum.dk

top - download

    Length: 3464 (0xd88)
    Types: TextFile
    Names: »Install.vms«

└─⟦a0efdde77⟧ Bits:30001252 EUUGD11 Tape, 1987 Spring Conference Helsinki
    └─ ⟦this⟧ »EUUGD11/gnu-31mar87/scheme/Install.vms« 

TextFile

	How to install a CScheme under VMS.

The following applies to VMS version 3.6.  Hopefully most will be
valid for later versions.  See section C below.

A) Description of the command files:

1) vmslogin.com:  This file sets up some convenient macros for
installing and running scheme.  You should probably "@" it before
starting. 

2) vmsscheme.com: This file is used only once scheme is linked.  It
allows scheme to be suspended (temporarily stopped) and later
proceeded.  The scheme DCL macro in vmslogin "@s" this file so that,
by default, scheme can be proceeded.  Note that this file always
invokes the scheme program with the band scheme.bin, so its definition
must be replaced (or a different macro used) if a different band is
desired.  In particular it gets in the way when generating a runtime
system.

3) vmsemacs.com: This file is similar to the above, except that it
allows both an editor and scheme to alternate in execution.  It
assumes that the editor (emacs) is suspended in the same way as
scheme.  Edit the file to include the file-name of the executable
version of the editor to run.

- The following files are needed only during installation

4) vmsall.com: This file takes care of most of the installation by
invoking in turn the rest of the files.

5) vmsccm.com: This file compiles a C source file using CCM_switches
as switches to the C compiler.  The DCL macro ccm invokes this file.

6) vmsfull.com: This file compiles all the C sources which will be
linked into a running scheme by invoking ccm on each file.

7) vmslink.com:  This file links all the object code files together
into an executable scheme program.

8) vmsutils.com: This file compiles and links the utility programs needed
to generate the system.

9) vmspsb.com: This file generates the binaries of the scheme sources.

B) Installation process:

1) Connect to the scheme directory (change the default directory to
the scheme directory).

2) "@" the file vmslogin.com.  Otherwise some of the later files will
not work.

3) "@" vmsall.com.  This creates the executable version of scheme, the
utility programs, and the scheme binaries.

4) Redefine the symbol scheme to be "$scm:scheme.exe -fasl runmd.bin".
This eliminates the definition in vmslogin.com which gets in the way
precisely here.

5) Run scheme by typing "scheme"

6) When the prompt (]=>) appears, optionally save the system by typing

	(save-world "bare.bin")
then (always) type 
	(load "featmd.bin" system-global-environment)
	(load "xbuild.bin" system-global-environment)

7) When the prompt reappears, optionally save the system by typing

	(disk-save "normal.bin")
then (always) type
	(load "sbuildmd.bin" system-global-environment)

8) When the prompt (]==>) appears, type

	(student-band "scheme.bin")
then type
	(exit)

9) Install scheme in the appropriate system directory.

10) "@" vmslogin.com a second time to obtain the original definition
of scheme.

11) To invoke scheme, type "scheme".  (Wasn't that easy?)

C) Other versions of VMS:

The VMS dependencies of CScheme are contained in vms*.h, and vms.c.

The only problem we know about for running CScheme under later
versions of VMS are the interrupt characters.  Some of the interrupt
characters scheme uses conflict (in later versions of VMS) with some
of the input editor command characters.  To change them so that they
do not conflict, look at the interrupt code (ugh!) in vms.c.  Have
fun!.

D) For more information, read the file README