Changes between Version 17 and Version 18 of BaseInstall

Timestamp:

Apr 28, 2009, 3:16:23 PM (16 years ago)

Author:

Christoph Mayer

Comment:

--

BaseInstall

@@ -8 +8 @@
 {{{
 > tar xfz ./ariba-x.x.x.tar.gz
-> cd ariba-x.x.x.tar.gz
+> cd ariba-x.x.x
 }}}
 
@@ -50 +50 @@
 Once the !PingPong sample is running and the nodes have connected, the initiator will send ping messages to the joined nodes every 2 seconds. You can now e.g. test mobility of Ariba and change the IP address of a node, or swith from LAN connection to WLAN. The Links established by the !PingPong sample through Ariba are mobility invariant and automatically repaired.
 
-== Prequisites ==
+== Prerequisites ==
 
 Ariba depends on libraries that may not be installed on your system: 
 
- * [http://www.boost.org Boost (version >=1.35)] 
+ * [http://www.boost.org Boost (version >=1.38)] 
  * [http://logging.apache.org/log4cxx Log4cxx (version >= 0.10.0)]
  * [http://gmplib.org GMP (no specific version)]
@@ -60 +60 @@
 Furthermore, you need default development tools - that are most likely already installed on your system - such as gcc, autoconf, automake, aclocal, libtool, liblt-dev ...
 
-If you installed some of the libraries locally and not system wide (e.g. using {{{./configure --prefix=MYPATH}}}, you have to tell Ariba where the libraries are installed. In this example we assume that (1) all libraries are installed locally, and not system wide, and (2) that you want to install Ariba locally. The installation process would then look as follow:
+=== Installing libraries locally ===
+
+We will shortly explain how to install the Boost and Log4cxx libraries locally on your system. Download Boost ({{{boost_1_38_0.tar.gz}}}) and Log4cxx (apache-log4cxx-0.10.0.tar.gz). Be aware, that Log4cxx requires the Apache Portable Runtime (libapr and libapr-util).
 
 {{{
+> cd ~/
+> mkdir local
+> cd boost_1_38_0
+> ./configure --prefix=/home/user/local
+> make install
+> cd ..
+> cd log4cxx-0.10.0
+> ./configure --prefix=/home/user/local
+> make install
+}}}
+
+If Boost makes itself a subdirectory (e.g. {{{/home/user/local/include/boost_1-38/boost}}}), move the {{{boost}}} directory one hierarchy up, resulting in {{{/home/user/local/include/boost}}}.
+
+There is a compiler optimization bug in gcc-4.3 that results in problems with Boost 1.38.0 (see https://svn.boost.org/trac/boost/ticket/2655). There is a workaround available, see https://svn.boost.org/trac/boost/changeset/51863/trunk/boost/xpressive/detail/core/adaptor.hpp. 
+
+If you installed some of the libraries locally and not system wide (e.g. using {{{./configure --prefix=MYPATH}}} as described above), you have to tell Ariba where the libraries are installed. In this example we assume that (1) all libraries are installed locally, and not system wide, and (2) that you want to install Ariba locally. The installation process would then look as follow:
+
+{{{
+> cd ~/ariba-x.x.x
 > mkdir build
 > ./configure 
-  --prefix=$PWD/build 
-  --with-boost=/home/user/libraries/boost_1_35_0/build   
-  CPPFLAGS='-I/home/user/libraries/gmp_4_2_2/build/include 
-  -I/home/user/libraries/log4cxx_0_10_0/build/include' 
-  LDFLAGS='-L/home/user/libraries/gmp_4_2_2/build/lib 
-  -L/home/user/libraries/log4cxx_0_10_0/build/lib 
-  -L/home/user/libraries/boost_1_35_0/build/lib'
+  --prefix=/home/user/ariba-x.x.x/build 
+  --with-boost=/home/user/local/include/boost   
+  CPPFLAGS='-I/home/user/local/include'
+  LDFLAGS='-L/home/user/local/lib'
 > make
 > make install