Once you have ftp'ed the archives, you need to do the following from the top-level directory to build and install the system:
$ gunzip < boot-architecture.tar.gz | tar xpof - $ rm boot-architecture.tar.gz $ cd boot-architecture
$ gunzip < ../m3cc.tar.gz | tar xpof - $ rm ../m3cc.tar.gz(Note: if you are going to be doing a port or installing the system for several platforms, save m3cc.tar.gz!)
The m3cc archive is not needed on Windows/NT or Windows 95, the so-called NT386 platform. The installation on that platform is not yet as smooth as the other platforms. Please see these NT386 installation notes for extra instructions on installing SRC Modula-3 on either of these platforms.
If your make does not support the VPATH feature, ensure that GNU_MAKE in your configuration template is set up to use GNU make. According to the GNU documentation, most BSD-based makes do support VPATH. If you're optimistic, skip this step and return here if the you have problems building m3cc. See m3cc/gcc/INSTALL for the gory details about VPATH.
$ ./m3boot $ ./m3ship $ cd ..
The m3ship step will copy the essential pieces of the bootstrap system to the directories (BIN_INSTALL, LIB_INSTALL, ...) specified in m3build/templates/architecture.
At this point, you may need to tell your shell that new executables (e.g. m3build and m3ship) are present, by resetting your PATH environment variable to include BIN_INSTALL and running rehash, for example.
Also, if you are using dynamic libraries and you set LIB_INSTALL in your configuration file to a directory that is not on your linker's normal search path, you will have to edit your LD_LIBRARY_PATH environment variable to point to that directory.
$ rm -rf boot-architecture
$ gunzip < m3.tar.gz | tar xpof - $ rm m3.tar.gz $ cd m3Read the README and follow any special instructions. In particular, edit src/m3makefile to select the components you want to build.
$ m3build $ cd .. $ rm -rf m3
The top-level m3makefile m3/src/m3makefile takes care of building each Modula-3 source package and shipping it. For your own packages you must run m3build and then explicitly run m3ship.
Note that the two deletion steps are optional, but do save space. Once the m3build step has completed, nothing in the xyz directory is needed.
Last modified on Mon Aug 12 10:41:46 PDT 1996 by heydon modified on Fri Jan 20 10:50:45 PST 1995 by kalsow modified on Thu Jan 7 18:40:11 PST 1993 by mullerCopyright (C) 1992, 1996, Digital Equipment Corporation. All rights reserved.