]>
Commit | Line | Data |
---|---|---|
18038256 | 1 | GNU Thales Installation |
2 | ======================= | |
2ace9480 | 3 | |
4 | Thales's installation is quite straightforward. | |
5 | - Untar the archive | |
6 | ||
7 | - cd to the directory newly created | |
8 | ||
9 | - ./configure | |
155ac5f5 | 10 | |
11 | * You need to have installed the packages with the files libmysqlclient.so | |
12 | and mysql.h. (with Debian, libmysqlclient-dev and libmysqlclient12) | |
13 | ||
2ace9480 | 14 | * You might want to use --with-mysql=PREFIX to specify where to look for mysql |
15 | includes and libraries. | |
155ac5f5 | 16 | |
2ace9480 | 17 | * You might also want to specify where thales will be installed. It defaults |
18 | to $HOME/thales, but can be forced using --prefix=DESTDIR. | |
155ac5f5 | 19 | |
2ace9480 | 20 | * You can specify the IRCD type on the command line. If you don't, you'll be |
21 | asked for it. Use --with-ircd=IRCDTYPE, where IRCDTYPE is bahamut, hybrid, | |
287805aa | 22 | ircdru, unreal, ultimate28 or ultimate30. |
155ac5f5 | 23 | |
2ace9480 | 24 | * If the compiled binary fails to work (often because of a linking problem), |
25 | you can try the --enable-static option, so that the generated binary will | |
26 | be statically linked. | |
155ac5f5 | 27 | |
2ace9480 | 28 | * If you don't want modes to be stored in the chan and user tables, use the |
29 | --enable-no-modes option. This will decrease CPU usage. Modes in the ison | |
30 | table will still be stored. | |
155ac5f5 | 31 | |
2ace9480 | 32 | * If you experience hashlist-related crashes, you might want to disable it. |
33 | Use --with-hashlist=NO, but thales will run 20% slower. | |
155ac5f5 | 34 | |
2ace9480 | 35 | * You can use different SQL tables names (Thales will use user, chan, ison, |
36 | server and maxvalues). See "Using Different Tables Names" below. | |
37 | ||
38 | - make (or gmake on BSD systems) | |
39 | ||
40 | - make install | |
41 | ||
42 | - cd to destination directory | |
43 | ||
44 | - edit thales.conf and configure everything | |
45 | ||
46 | - create the mysql database if needed | |
47 | ||
48 | - load the tables (usually with mysql -u user -p database < mysql-IRCDTYPE.sql | |
49 | ||
50 | - add the C/N lines for Thales in your ircd.conf. No U lines are needed. | |
51 | ||
52 | - start thales : ./thales | |
53 | It runs in the background. to run it in the | |
54 | foreground, use -d. To provide a verbose log (always interesting to see how | |
55 | it works), use -v. | |
56 | If thales doesn't start because of a libmysqlclient problem, your mysql | |
57 | installation is bogus. Try to compile it statically (see above : | |
58 | --enable-static). | |
59 | ||
60 | - enjoy :) | |
61 | ||
62 | Using Different Tables Names | |
63 | ============================ | |
64 | If for some reason, you can't use the tables named user, chan, ison, server and | |
65 | maxvalues for Thales (if the database is shared with another application, for | |
66 | example), you can change this. | |
67 | - (Optionnally) Change the table names prefix with | |
68 | ./configure --with-tableprefix=blop_ (tables will be named blop_chan etc) | |
69 | - Change the name of the tables in the data/mysql-*.sql file for your ircd, and | |
70 | load the file into MySQL to create the tables. Alternatively, you can rename | |
71 | the existing Thales tables with ALTER TABLE oldname RENAME AS newname; | |
72 | - Edit src/db.h, and modify TBL_USER, TBL_CHAN, TBL_ISON, and/or TBL_MAXV. | |
73 | - Recompile Thales. | |
74 | ||
75 | Please note that all your scripts will probably need modifications too. | |
76 | ||
77 | ------------------------------------------------------------------------- | |
78 | Here are the autoconf instrutions, if you need more info about the | |
79 | installation process. | |
80 | ||
81 | Basic Installation | |
82 | ================== | |
83 | ||
84 | These are generic installation instructions. | |
85 | ||
86 | The `configure' shell script attempts to guess correct values for | |
87 | various system-dependent variables used during compilation. It uses | |
88 | those values to create a `Makefile' in each directory of the package. | |
89 | It may also create one or more `.h' files containing system-dependent | |
90 | definitions. Finally, it creates a shell script `config.status' that | |
91 | you can run in the future to recreate the current configuration, a file | |
92 | `config.cache' that saves the results of its tests to speed up | |
93 | reconfiguring, and a file `config.log' containing compiler output | |
94 | (useful mainly for debugging `configure'). | |
95 | ||
96 | If you need to do unusual things to compile the package, please try | |
97 | to figure out how `configure' could check whether to do them, and mail | |
98 | diffs or instructions to the address given in the `README' so they can | |
99 | be considered for the next release. If at some point `config.cache' | |
100 | contains results you don't want to keep, you may remove or edit it. | |
101 | ||
102 | The file `configure.in' is used to create `configure' by a program | |
103 | called `autoconf'. You only need `configure.in' if you want to change | |
104 | it or regenerate `configure' using a newer version of `autoconf'. | |
105 | ||
106 | The simplest way to compile this package is: | |
107 | ||
108 | 1. `cd' to the directory containing the package's source code and type | |
109 | `./configure' to configure the package for your system. If you're | |
110 | using `csh' on an old version of System V, you might need to type | |
111 | `sh ./configure' instead to prevent `csh' from trying to execute | |
112 | `configure' itself. | |
113 | ||
114 | Running `configure' takes awhile. While running, it prints some | |
115 | messages telling which features it is checking for. | |
116 | ||
117 | 2. Type `make' to compile the package. | |
118 | ||
119 | 3. Optionally, type `make check' to run any self-tests that come with | |
120 | the package. | |
121 | ||
122 | 4. Type `make install' to install the programs and any data files and | |
123 | documentation. | |
124 | ||
125 | 5. You can remove the program binaries and object files from the | |
126 | source code directory by typing `make clean'. To also remove the | |
127 | files that `configure' created (so you can compile the package for | |
128 | a different kind of computer), type `make distclean'. There is | |
129 | also a `make maintainer-clean' target, but that is intended mainly | |
130 | for the package's developers. If you use it, you may have to get | |
131 | all sorts of other programs in order to regenerate files that came | |
132 | with the distribution. | |
133 | ||
134 | Compilers and Options | |
135 | ===================== | |
136 | ||
137 | Some systems require unusual options for compilation or linking that | |
138 | the `configure' script does not know about. You can give `configure' | |
139 | initial values for variables by setting them in the environment. Using | |
140 | a Bourne-compatible shell, you can do that on the command line like | |
141 | this: | |
142 | CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure | |
143 | ||
144 | Or on systems that have the `env' program, you can do it like this: | |
145 | env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure | |
146 | ||
147 | Compiling For Multiple Architectures | |
148 | ==================================== | |
149 | ||
150 | You can compile the package for more than one kind of computer at the | |
151 | same time, by placing the object files for each architecture in their | |
152 | own directory. To do this, you must use a version of `make' that | |
153 | supports the `VPATH' variable, such as GNU `make'. `cd' to the | |
154 | directory where you want the object files and executables to go and run | |
155 | the `configure' script. `configure' automatically checks for the | |
156 | source code in the directory that `configure' is in and in `..'. | |
157 | ||
158 | If you have to use a `make' that does not supports the `VPATH' | |
159 | variable, you have to compile the package for one architecture at a time | |
160 | in the source code directory. After you have installed the package for | |
161 | one architecture, use `make distclean' before reconfiguring for another | |
162 | architecture. | |
163 | ||
164 | Installation Names | |
165 | ================== | |
166 | ||
167 | By default, `make install' will install the package's files in | |
168 | `/usr/local/bin', `/usr/local/man', etc. You can specify an | |
169 | installation prefix other than `/usr/local' by giving `configure' the | |
170 | option `--prefix=PATH'. | |
171 | ||
172 | You can specify separate installation prefixes for | |
173 | architecture-specific files and architecture-independent files. If you | |
174 | give `configure' the option `--exec-prefix=PATH', the package will use | |
175 | PATH as the prefix for installing programs and libraries. | |
176 | Documentation and other data files will still use the regular prefix. | |
177 | ||
178 | In addition, if you use an unusual directory layout you can give | |
179 | options like `--bindir=PATH' to specify different values for particular | |
180 | kinds of files. Run `configure --help' for a list of the directories | |
181 | you can set and what kinds of files go in them. | |
182 | ||
183 | If the package supports it, you can cause programs to be installed | |
184 | with an extra prefix or suffix on their names by giving `configure' the | |
185 | option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. | |
186 | ||
187 | Optional Features | |
188 | ================= | |
189 | ||
190 | Some packages pay attention to `--enable-FEATURE' options to | |
191 | `configure', where FEATURE indicates an optional part of the package. | |
192 | They may also pay attention to `--with-PACKAGE' options, where PACKAGE | |
193 | is something like `gnu-as' or `x' (for the X Window System). The | |
194 | `README' should mention any `--enable-' and `--with-' options that the | |
195 | package recognizes. | |
196 | ||
197 | For packages that use the X Window System, `configure' can usually | |
198 | find the X include and library files automatically, but if it doesn't, | |
199 | you can use the `configure' options `--x-includes=DIR' and | |
200 | `--x-libraries=DIR' to specify their locations. | |
201 | ||
202 | Specifying the System Type | |
203 | ========================== | |
204 | ||
205 | There may be some features `configure' can not figure out | |
206 | automatically, but needs to determine by the type of host the package | |
207 | will run on. Usually `configure' can figure that out, but if it prints | |
208 | a message saying it can not guess the host type, give it the | |
209 | `--host=TYPE' option. TYPE can either be a short name for the system | |
210 | type, such as `sun4', or a canonical name with three fields: | |
211 | CPU-COMPANY-SYSTEM | |
212 | ||
213 | See the file `config.sub' for the possible values of each field. If | |
214 | `config.sub' isn't included in this package, then this package doesn't | |
215 | need to know the host type. | |
216 | ||
217 | If you are building compiler tools for cross-compiling, you can also | |
218 | use the `--target=TYPE' option to select the type of system they will | |
219 | produce code for and the `--build=TYPE' option to select the type of | |
220 | system on which you are compiling the package. | |
221 | ||
222 | Sharing Defaults | |
223 | ================ | |
224 | ||
225 | If you want to set default values for `configure' scripts to share, | |
226 | you can create a site shell script called `config.site' that gives | |
227 | default values for variables like `CC', `cache_file', and `prefix'. | |
228 | `configure' looks for `PREFIX/share/config.site' if it exists, then | |
229 | `PREFIX/etc/config.site' if it exists. Or, you can set the | |
230 | `CONFIG_SITE' environment variable to the location of the site script. | |
231 | A warning: not all `configure' scripts look for a site script. | |
232 | ||
233 | Operation Controls | |
234 | ================== | |
235 | ||
236 | `configure' recognizes the following options to control how it | |
237 | operates. | |
238 | ||
239 | `--cache-file=FILE' | |
240 | Use and save the results of the tests in FILE instead of | |
241 | `./config.cache'. Set FILE to `/dev/null' to disable caching, for | |
242 | debugging `configure'. | |
243 | ||
244 | `--help' | |
245 | Print a summary of the options to `configure', and exit. | |
246 | ||
247 | `--quiet' | |
248 | `--silent' | |
249 | `-q' | |
250 | Do not print messages saying which checks are being made. To | |
251 | suppress all normal output, redirect it to `/dev/null' (any error | |
252 | messages will still be shown). | |
253 | ||
254 | `--srcdir=DIR' | |
255 | Look for the package's source code in directory DIR. Usually | |
256 | `configure' can determine that directory automatically. | |
257 | ||
258 | `--version' | |
259 | Print the version of Autoconf used to generate the `configure' | |
260 | script, and exit. | |
261 | ||
262 | `configure' also accepts some other, not widely useful, options. |