X-Git-Url: http://git.pk910.de/?p=srvx.git;a=blobdiff_plain;f=INSTALL;h=e74bb49bae4c6759ae4b57ce60d9ccbc1c5a8745;hp=0106b2363a5d2a2d0cf73777e0b89136756d9fb1;hb=80d9ed728be4b02ac483f3339cbb184f6602d15b;hpb=222e1b0003536cf7b47858961d4b56d45c6d6606 diff --git a/INSTALL b/INSTALL index 0106b23..e74bb49 100644 --- a/INSTALL +++ b/INSTALL @@ -14,11 +14,12 @@ files. Requirements: ---------- -This release of srvx (1.2) only supports the Undernet P10 and Bahamut +This release of srvx (1.3) only supports the Undernet P10 and Bahamut protocols and is known to link with ircu/Universal (u2.10.09), ircu/Undernet (u2.10.10, u2.10.11), ircu-lain, and Bahamut 1.4.32. It does not support hybrid, Unreal, or any other ircd not listed. Should -you find other compatible ircds, please let us know. +you find other compatible ircds, please let us know. Most of the +testing has been done on ircu2.10.11.06. srvx is known to compile on the following systems as long as you are using GNU make (make on Linux, gmake on many other systems): @@ -48,6 +49,14 @@ You may also have trouble unless your compiler's C preprocessor supports ISO C99 varadic macros. gcc is the compiler we use for almost all our testing, and we recommend it for use with srvx. +PreInstall: +---------- +$ aclocal +$ autoconf +$ autoreconf -f -i -Wall,no-obsolete +$ cp /usr/share/libtool/* ./ +$ automake + Quick Install: ---------- $ ./configure @@ -96,17 +105,10 @@ Compiling: 8) Copy srvx.conf.example to srvx.conf and edit to suit your needs. Errors in the configuration file will be logged to main.log (and if srvx is running in the foreground, printed to - stdout) when you start the daemon. If you disable nick ownership - or enable the email features, you should copy srvx.conf to the - src directory and re-run make; this will regenerate the help - files (especially for NickServ) to include the appropriate - entries. - - You can also do this by hand using the expnhelp program in src: - ./src/expnhelp < nickserv.help.m4 > nickserv.help + stdout) when you start the daemon. 9) You can now begin using your service bots. You can debug by - running it with '-fV', it will not background itself, and it + running it with '-fd', it will not background itself, and it will be fairly verbose if you gave the configure script the --enable-debug flag. If you would like to run in the foreground with no verbosity, use the '-f' flag. If you just want to run it,