User guide

12.1. LINUX INSTALLATION 207
to the end of the file .bashrc in your home directory so the the BCPL environment
variables are automatically setup whenever you start a bash shell.
4) Now change directory to cintcode and attempt to re-build the parts of the sys-
tem implemented i n C and populate the directory cin with a basic set of compiled
commands.
cd distribution/BCPL/cintcode
make clean
make sys
If the system is known to work typing just make instead of make sys is more
convenient. The line make clean is a recent addition that eliminates some commonly
reported problems.
If th er e was a problem, check the all the C code compiled correctly an d linked to
form the executable cintsys. Then try typing the following shell command:
cintsys -f -v
or
cintsys -f -vv
and study the output, in conjunct i on with sysc/cintsys.c and sysb/boot.b. Hope-
fully, there will be enough information there to diagnose and correct the problem. It
includes, in particul ar, a trace of all uses of the shell environment variables which are
a common sour c e of trouble.
If bin/cintsys has been successfully built, it should be possible to enter the system
by typing: cintsys or bin/cintsys.
bin/cintsys
BCPL Cintcode System (20 Jan 2011)
0.000>
The basic set of commands initially provided are: abort, bcpl, c, cmpltest, echo,
logout and map. A simple test of the system is to type:
echo hello
map pic
cmpltest
bcpl com/bcpl.b to junk
junk com/bcpl.b to junk
5) If the above tests are successful, recompile all the system software and commands
by typing: