X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdbuild.pod;h=5fe138d701b9f4e7224bd42a3b872c247963765d;hb=9dba554e59319d13076a8184c7889cca868b4c85;hp=f364aa2448799e35957c295b83cb7597a057a219;hpb=c1a96caa82a48ed49a02c92e9d79e93b95ef3b06;p=rrdtool.git

diff --git a/doc/rrdbuild.pod b/doc/rrdbuild.pod
index f364aa2..5fe138d 100644
--- a/doc/rrdbuild.pod
+++ b/doc/rrdbuild.pod
@@ -15,9 +15,9 @@ ones before you can build RRDtool.
 
 This document will tell you about all the necessary steps to get going.
 
-These instructions assume you are using a bash shell. If you use csh/tcsh,
-then you can either type 'bash' to switch to bash for the compilation or if
-you know what you are doing just replace replace the export bits with
+These instructions assume you are using a B<bash> shell. If you use csh/tcsh,
+then you can either type F<bash> to switch to bash for the compilation or if
+you know what you are doing just replace the export bits with
 setenv.
 
 We further assume that your copies of B<tar> and B<make> are actually B<GNU
@@ -41,15 +41,10 @@ Where you want to install the software.
 =back
 
 Once you have decided. Save the two locations into environment variables.
-Depending on the shell you are using, you can do either (bash,zsh):
 
  BUILD_DIR=/tmp/rrdbuild
  INSTALL_DIR=/usr/local/rrdtool-1.2.99907080300
 
-Or if you run tcsh:
-
- set BUILD_DIR=/tmp/rrdbuild
- set INSTALL_DIR=/usr/local/rrdtool-1.2.99907080300
 
 If your F</tmp> is mounted with the option noexec (RHEL seems todo that) you have to choose
 a different directory!
@@ -61,6 +56,7 @@ Now make sure the BUILD_DIR exists and go there:
 
 Lets first assume you already have all the necessary libraries
 pre-installed. 
+
  wget http://oss.oetiker.ch/rrdtool/pub/rrdtool-1.2.99907080300.tar.gz
  gunzip -c rrdtool-1.2.99907080300.tar.gz | tar xf -
  cd rrdtool-1.2.99907080300
@@ -74,7 +70,11 @@ package for each library you install. Once you have the missing bits on
 board, just re-run the last line of the instructions above.
 
 But again this may have been too optimistic, and you actually have to
-compile your own copies of the required libraries.
+compile your own copies of some of the required libraries. Things like
+libpng and zlib are pretty standard so you will probably have them on your
+system anyway. Freetype, Fontinst, Cairo, Pango may be installed, but it is
+possible that they are pretty old and thus don't live up to the
+expectations, so you may want to compile their latest versions.
 
 =head3 Build Tipps for AIX
 
@@ -112,7 +112,31 @@ set the following environamen variable
 
  export PKG_CONFIG_PATH=${INSTALL_DIR}/lib/pkgconfig
  export PATH=$INSTALL_DIR/bin:$PATH
+
+Since we are compiling libraries dynamically, you they must further know
+where to find each other. This is done by setting an appropriate LDFLAG.
+Unfortunatly the syntax differs from system to system:
+
+=over
+
+=item Solaris
+
+ export LDFLAGS=-R${INSTALL_DIR}/lib 
+
+=item Linux
+
+ export LDFLAGS="-Wl,--rpath -Wl,${INSTALL_DIR}/lib" 
+
+=item HPUX
  
+ export LDFLAGS="+b${INSTALL_DIR}/lib"
+
+=item AIX
+
+ export LDFLAGS="-Wl,-blibpath:${INSTALL_DIR}/lib"
+
+=back 
+
 If you have GNUmake installed and it is not called 'make',
 then do
 
@@ -158,13 +182,13 @@ the end of line 4 means that line 4 and line 5 are on one line.
  gunzip -c freetype-2.3.5.tar.gz | tar xf -
  cd freetype-2.3.5
  ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC"
- $MAKE   (or gmake)
- $MAKE install (or gmake install)
+ $MAKE
+ $MAKE install
 
 If you run into problems building freetype on Solaris, you may want to try to
 add the following at the start the configure line:
 
- env GNUMAKE=gmake EGREP=egrep
+ env EGREP=egrep
 
 =item Building fontconfig
 
@@ -215,6 +239,16 @@ config file.
  $MAKE
  $MAKE install
 
+=item Building LibXML2
+
+ cd $BUILD_DIR
+ wget http://oss.oetiker.ch/rrdtool/pub/libs/libxml2-sources-2.6.31.tar.gz
+ gunzip -c libxml2-sources-2.6.31.tar.gz | tar xf -
+ cd libxml2-sources-2.6.31
+ ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC"
+ $MAKE
+ $MAKE install
+
 =back
 
 Now all the dependent libraries are built and you can try again. This time
@@ -222,11 +256,6 @@ you tell configure where it should be looking for libraries and include
 files. This is done via environment variables. Depending on the shell you
 are running, the syntax for setting environment variables is different.
 
- CPPFLAGS=-I$INSTALL_DIR/include
- LDFLAGS="-R$INSTALL_DIR/lib -L$INSTALL_DIR/lib"
- CFLAGS=-O3
- export CPPFLAGS LDFLAGS CFLAGS
-
 And finally try building again. We disable the python and tcl bindings
 because it seems that a fair number of people have ill configured python and
 tcl setups that would prevent rrdtool from building if they are included in