X-Git-Url: http://git.silcnet.org/gitweb/?p=runtime.git;a=blobdiff_plain;f=INSTALL;h=370c15318b400ceb3ce8d34d85d3d145231b57a0;hp=1236d92ec685606bdab9597241b2ba57852b15df;hb=HEAD;hpb=e8b3711134ef37555deb444a44664302c6aaaaed

diff --git a/INSTALL b/INSTALL
index 1236d92e..370c1531 100644
--- a/INSTALL
+++ b/INSTALL
@@ -1,32 +1,21 @@
 Quick Installation
 ==================
 
-   To configure and compile SILC package give the comands:
+   To configure and compile SILC Runtime Toolkit give the commands:
 
 	./configure
-	make (or gmake, GNU make is required)
+	make
 	make install
 
-   This will install the SILC binaries and configuration files into the
-/usr/local/silc/ directory.  System wide configuration files are installed
-into the /etc/silc/ directory.
-
-Some Configuration Options
-==========================
+Configuration Options
+=====================
 
    You can give various options to the `configure' shell script.  You should
 give --help command to the `configure' to see all of them.  Here is listed
 few options that you might want to use.  Please refer to the rest of this
 file for more generic installation instructions.
 
-`--with-gmp[=DIR]'
-
-   If you wish to use GMP library for arbitrary precision arithmetic
-library instead of using the MPI library included in the package, you can
-give the --with-gmp[=DIR] option to the `configure'.  The DIR is the upper
-path in your system which contains lib/ and include/ for GMP library.
-
-'--with-iconv[=DIR]'
+`--with-iconv[=DIR]'
 
    If your system doesn't provide iconv() function in its native libraries
 (usually libc) or if this function is broken (e.g. older Solaris systems),
@@ -57,6 +46,16 @@ you can give this option to the `configure'.
 However, if it fails, but you still want to compile in the IPv6 support
 you can give --enable-ipv6 option to force the IPv6 support.
 
+`--disable-cpu-optimizations'
+ 
+   By default the configure script will attempt to detect the type of your 
+CPU and enable any features specific to your CPU that could optimize the 
+performance of the Toolkit. If you are creating binary package that should 
+work on any CPU (and not only your CPU) you should diable these 
+optimizations. If you compile it for yourself only, keeping the 
+optimizations enabled is recommended.
+ 
+
 Basic Installation
 ==================