Next: The pC++ Programming
Up: Installing the System.
Previous: Installing the System.
Get the most up-to-date version from the FTP archive. Use ``finger
email@example.com'' to learn about the current version and where to
- Move the archive to the directory where tar will create the
distribution directory. A good choice is /usr/local/src (if you are
root) or your home directory (if you are a user).
- execute gzip -d -c <distribution>-*.tar.gz | tar xvf -
- From within the distribution directory, run the ./configure
script. This will automatically modify the Makefiles to include the
correct libraries and/or compile flags for your architecture. You can
override the defaults with ./configure -cfront, or
./configure -gnu. You may also choose compilers with
./configure -cc=cc -c++=CC. You may specify the architecture
as the last parameter if ./configure cannot automatically determine it.
Please inform us if there are other modifications required for your
system. Running ``./configure unknown'' will return files to their
- make install At this point, simply running ``make'' will NOT
work; ``make install'' is required. This will invoke a recursive make
for each of the source subdirectories.
If you are using a supported parallel machine, the machine specific
runtime module will also be compiled. ./TestSuite will also be
compiled for uniprocessor simulation. See ./TestSuite/README. If all
went well, you should be ready to test the uniprocessor version with
``cd TestSuite; make test''.
- Reprint this user manuals in ./doc (See the ./doc/README)
because it may have changed.
- You may ``make clean'' after you have installed the system to
remove all the .o files, and really save on disk space. The libraries
(*.a) and binaries will be preserved until you ``make cleaninstall'',
which gets rid of everything but the source code.