Go to the previous, next section.

Installation of ILU

This document describes the installation of version 1.6.4 of the Inter-Language Unification (ILU) system.

Installing on a UNIX System

Prerequisites

ILU requires the imake program from the MIT X Consortium release of the X Window System, version 4 or later. This is available via FTP from the ftp servers ftp.x.org on the East Coast, or gatekeeper.dec.com on the West Coast.

The stubbers for ILU use the GNU program bison, which may be obtained via FTP from prep.ai.mit.edu, in `pub/gnu/bison-1.xx.tar.Z'. However, the release as distributed provides a C version of the parser, so it is not necessary to have bison at your site.

You will need an ANSI C compiler to build and install ILU, along with an ANSI C-compliant `libc.a'. We find that GNU GCC combined with the GNU C Library, used in ANSI/POSIX mode, works fine, unless you are building the Modula-3 support. The SunOS runtime library for release 2.8 of Modula-3 hard-codes in dependencies on Sun include files, so they must be used.

ILU provides support for a number of languages, currently ANSI C, C++, Modula-3, and Common Lisp.

No standard "name service" or binding service is provided. We feel that this is an area to be addressed independently, and we may include a name service in future releases of ILU. An experimental name service interface can be seen in the ANSI C (ILU_C_PublishObject, ILU_C_WithdrawObject, and ILU_C_LookupObject) and Common Lisp support (ilu:publish, ilu:withdraw, and ilu:lookup), but this is not guaranteed to be present in future releases.

ILU documentation is provided in a pre-formatted form, PostScript. The source form of the documentation is called TIM, and is documented in `ILUSRC/doc/tim.ps'. It uses TeX for document formatting, but you should not need to rebuild the documentation. If for some reason you do need to rebuild the documentation, you should have the system TeX; the file `ILUSRC/doc/texinfo2.ps' contains information about obtaining TeX.

Configuration

Begin by creating two directories: one, ILUHOME, to install the ILU in, and the other, ILUSRC, to unpack the sources in, and build the system in. It is often convenient if ILUSRC is a sub-directory of ILUHOME, but it is not necessary. At PARC, we use `/import/ilu' for ILUHOME, and `/import/ilu/src' for ILUSRC.

Copy the tar file `ilu-1.6.4.tar' or `ilu-1.6.4.tar.Z' to ILUSRC. Uncompress it if necessary with the uncompress program:

% uncompress ilu-1.6.4.tar.Z

Then unpack the tar file:

% tar xf ilu-1.6.4.tar

Next, edit the file ILUSRC/makefile.dist to change the value of the variable IMAKE to point to your imake program.

After that, copy the file `ILUSRC/imake/local.defs.default' to `ILUSRC/imake/local.defs'. Then configure the distribution by editing `ILUSRC/imake/local.defs' to define the configuration of your system. The following variables need to be set:

If you are going to have a need to build the documentation, you should also define the following:

Next, you should decide which transports you wish to build. The options are in-memory (keyword INMEMORY), UDP datagrams (keyword UDPSOCKET), and TCP/IP sockets (keyword TCPSOCKET). (Currently, we recommend building only the TCPSOCKET transport.) For each transport that you wish to build, add a line

#define ADD_transport-keyword_TRANSPORT 1

Do the same for RPC protocols. The current choices are Sun RPC (keyword SUNRPC). For each protocol that you wish to include, add a line

#define ADD_protocol-keyword_PROTOCOL 1

Do the same for programming languages. The current choices are C++ (keyword CPLUSPLUS), C (keyword C), Modula-3 (keyword MODULA3), and Common Lisp (keyword COMMONLISP). (We recommend building only those languages you are actually interested in using.) For each language that you decide to include, add a line

#define ADD_language-keyword_LANGUAGE 1
If you are building support for Common Lisp, you will need to specify the command which invokes your Common Lisp program in batch mode, as the value of the variable LISP_BATCH_COMMAND, and the name of the binary or fasl file extension as the value of the variable LISP_BIN_EXT. If you are building support for C++, you should define the command to compile a C++ file as the value of the variable CPLUSPLUS_COMMAND. If you are building support for Modula-3, you should define the command to compile a Modula-3 file as the value of the variable M3_COMMAND, and consider whether you like the definition of the variable M3DEBUGFLAGS. If you choose to build the ANSI C support, the same compile command will be used compile a C file as you have defined for the value of ANSI_C_COMPILER.

You may need to add other defines to include various libraries, but probably not. If so, examine the file `ILUSRC/imake/ilu.rules' to see what the possibilities are.

If you are not using SunOS 4.x, you may have to edit the definitions of AR, CC, and so on in the file `ILUSRC/imake/ilu.defs'. This file will probably be automatically constructed by GNU autoconf in future releases. In particular, SVR4 releases such as Sun's Solaris 2.3 and SGI's IRIX 5.2 seem to need the following definitions:

   AR = ar r
   RANLIB = touch
and possibly others.

Building

Now that you have configured the release, do the following to build the system. Note that the capitalization of the arguments to make is important.

  1. Set your working directory to ILUSRC:
    % cd ILUSRC
    

  2. Build the Makefiles with the following commands:
    % make -f makefile.dist
    % make Makefiles
    

  3. Build the system with the command:
    % make
    

  4. If the build goes well, install the system with the command
    % make Install
    

  5. After the installation is complete, you may remove extra files in ILUSRC with the command
    % make Clean
    
    You may wish to use make Clean at any time, to get your system into a consistent state.

  6. If you change the configuration files, you should clean the system with the command `make Clean', and redo the installation starting at step 2. If you run into problems that can be fixed without changing the configuration files, you can re-build the system by starting at step 3.

Environment Variables

ILU tools use a number of UNIX environment variables under the covers.

Examples

If you are interested in working with Common Lisp, we recommend starting with the example system in `ILUHOME/examples/fs/'. If you are interested in working with Modula-3, we recommend starting with the example system in `ILUHOME/examples/foogen/'. If you are interested in working with ANSI C, we recommend starting with the example system in `ILUHOME/examples/test1/'. If you are interested in working with C++, we recommend starting with the example system in `ILUHOME/examples/rwho2/'. Read the `README' file in each directory first.

Bug Reporting and Comments

Report bugs (nah! -- couldn't be!) to the Internet address ilu-bugs.parc@xerox.com, or to the XNS address ILU-bugs:PARC:Xerox. Bug reports are more helpful with some information about the activity; please read section Debugging ILU Programs, for more information on how to look at problems. General comments and suggestions can be sent to either ILU@parc.xerox.com or ILU-bugs.

Go to the previous, next section.