-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
129 lines (96 loc) · 5.07 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
Installation Instructions for Ulm's Oberon Library and the included
Compiler for the Intel Architecture.
Warning: This is alpha software. Some components of this package have
not been extensively tested, some of them are just plain experimental
or of temporary nature. This release provides an early access to the
current state of development for the impatient. Error reports and
suggestions are nevertheless welcome (see below for details).
Yet another warning: Do not try to run this package on systems with
less than 256 MB physical main memory. Unfortunately systems with
less physical memory can be more or less deadlocked with swapping.
(1) Unpack this archive and cd to its top-level directory.
(2) Decide where to install this package. A good candidate would
be /usr/local/oberon but you are also free to chose another
directory like $HOME/oberon if you prefer a private installation.
Set the environment variable OBERON to this directory.
(Please do not select an already used directory like /usr/local;
if you want to find the binaries in /usr/local/bin, you are
free to set BinDir to /usr/local/bin in the make command line
below).
(3) Invoke GNU make:
make DestDir=$OBERON
(Note that you need libelf installed on your system. Otherwise
the compilation of tof2elf will fail. We have also noticed broken
libelf installations where tof2elf crashed immediately due to a
failed assertion within the libelf library. In case you are unable
to create a working tof2elf yourself, you can download a static
binary from
ftp://ftp.mathematik.uni-ulm.de/pub/soft/oberon/ulm/i386/tof2elf
using
make download_tof2elf
but be warned that this binary is larger than this entire package).
(4) Start the Oberon Name Server. This is a simple directory service
that is used by cdbd and its clients later. To start this server
run $OBERON/bin/start_pons. This must be done each time the machine
is rebooted.
Alternatively, you are free to generate scripts in /etc/init.d
that start pons and cdbd (see next paragraph) automatically.
This is currently supported for SuSE Linux only:
make DestDir=$OBERON \
InitDir=/etc/init.d InstallInitDir=/etc/init.d suserun
(5) This step is to be skipped if /etc/init.d/cdbd has been
installed by the previous step.
Start the Compiler Database Daemon. The compiler loads source
files from the database and stores its results to the database.
Run the the script $OBERON/bin/start_cdbd to start this daemon.
This must be done each time when the machine is rebooted.
Don't be surprised if oberon.db becomes quite huge over time. Unless
you delete the file oberon.db it should not be necessary to repeat
the following steps after a reboot.
(6) Load all library sources into the database maintained by cdbd
using the utility load_libsources:
$OBERON/bin/load_libsources
This needs to be done once only.
(7) To include $OBERON/bin in your PATH, $OBERON/man in your
MANPATH, and setting ONS_ROOT so that the name space of your
Oberon Name Server is found, following script needs to
be sourced:
. $OBERON/rc
You might want to include this script into /etc/profile or
~/.profile. (Under Gentoo it is recommended to copy this
script into the /etc/env.d directory and to run env-update
afterwards).
(8) You might want to check the selection of the intensity parameter
for cdbd and obload. See TUNING for details.
(9) You might want to run a steady-state test. Instructions are
to be found in the file STEADY-STATE-TEST.
(10) Enjoy.
To compile your own programs do the following:
(1) Setup a directory for each project. Definitions should end
in ``.od'' and modules in ``.om''. The basename of the file
names should be derived from the module names. Conflicts to
names of library modules should be avoided.
(You might want to try this first with Welcome.o[dm] that
are shipped within the root directory of this package).
(2) Check in all source files into the database:
obci *.o[dm]
Whenever sources change, they need to be checked in again.
It does not harm to check in sources that are already in the
database.
(3) Build programs by passing the name of your main module to
obbuild:
obbuild MyMainModule
Note that the compiler finds all other modules required within
the database and compiles them as well if this has not been
done before. Please note also that the name of the main module
is given without its extension (``.od'' or ``.om'').
Error messages are sent to standard error. In case of success,
an executable binary that is named after the main module is stored
into the current directory.
Please send bug reports and feature requests to
oberon@mathematik.uni-ulm.de. If the request is purely specific
to the Linux/i386 platform you may as well send the mail to
ehrhardt@mathematik.uni-ulm.de. Sending spams (unsolicited commercial
emails, bulk emails, viruses or other junk) to these addresses is
prohibited.
Andreas Borchert and Christian Ehrhardt