X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=doc%2Frrdbuild.pod;h=308115aa72165995faa62f3d283d64354f6935c3;hb=aa4d951ab71eb7fe57840c3baaddf36809806aef;hp=a7cf9e6ae3d77fbcbd48cf0e4e7f79d4e24529c2;hpb=ac6b11cccdcc91b157be327e526f5f1f16b45f8c;p=rrdtool.git

diff --git a/doc/rrdbuild.pod b/doc/rrdbuild.pod
index a7cf9e6..308115a 100644
--- a/doc/rrdbuild.pod
+++ b/doc/rrdbuild.pod
@@ -35,12 +35,12 @@ 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.8
+ INSTALL_DIR=/usr/local/rrdtool-1.2.10
 
 Or if you run tcsh:
 
  set BUILD_DIR=/tmp/rrdbuild
- set INSTALL_DIR=/usr/local/rrdtool-1.2.8
+ set INSTALL_DIR=/usr/local/rrdtool-1.2.10
 
 Now make sure the BUILD_DIR exists and go there:
 
@@ -52,10 +52,10 @@ per-installed. Note that these instructions assume that your copies of
 B<tar> and B<make> are actually B<GNU tar> and B<GNU make> respectively. It
 could be that they are installed as B<gtar> and B<gmake> on your system.
 
- wget http://people.ee.ethz.ch/oetiker/webtools/rrdtool/pub/rrdtool-1.2.8.tar.gz
- tar zxf rrdtool-1.2.8.tar.gz
- cd rrdtool-1.2.8
- ./configure --prefix=/path/to/installation && make && make install
+ wget http://people.ee.ethz.ch/oetiker/webtools/rrdtool/pub/rrdtool-1.2.10.tar.gz
+ tar zxf rrdtool-1.2.10.tar.gz
+ cd rrdtool-1.2.10
+ ./configure --prefix=$INSTALL_DIR && make && make install
 
 Ok, this was very optimistic. This try will probably have ended with
 B<configure> complaining about several missing libraries. If you are on a
@@ -75,6 +75,13 @@ compile your own copies of the required libraries. Here is how:
  wget http://people.ee.ethz.ch/oetiker/webtools/rrdtool/pub/libs/cgilib-0.5.tar.gz
  tar zxf cgilib-0.5.tar.gz
  cd cgilib-0.5
+
+If you are on Mac OSX you want to fix a little header problem here by doing
+
+ touch malloc.h
+
+and now you are ready to build
+
  make CC=gcc CFLAGS="-O3 -fPIC -I."
  mkdir -p $BUILD_DIR/lb/include
  cp *.h $BUILD_DIR/lb/include
@@ -118,11 +125,11 @@ the end of line 4 means that line 4 and line 5 are on one line.
  make
  make install
 
-
 =item Building libart_lgpl
 
  cd $BUILD_DIR
  wget http://people.ee.ethz.ch/oetiker/webtools/rrdtool/pub/libs/libart_lgpl-2.3.17.tar.gz
+ tar zxvf libart_lgpl-2.3.17.tar.gz
  cd libart_lgpl-2.3.17
  env CFLAGS="-O3 -fPIC" ./configure --disable-shared --prefix=$BUILD_DIR/lb
  make
@@ -130,10 +137,17 @@ the end of line 4 means that line 4 and line 5 are on one line.
 
 =back
 
-Now all the dependent libraries are built and you can try again. This time
-you tell configure where it should be looking for libraries and include
-files. This is done via environment variables. Depending on the shellyou are running, the syntax for setting
-environment variables is different. Under csh/tcsh you use:
+Now all the dependent libraries are built and you can try again. Since these
+are static libraries, you may have to use F<ranlib> to make them accessible.
+Especially BSD systems like Mac OS X may require this, Linux and Solaris
+will do just fine without since their F<ar> command does ranlibs job as well.
+
+ ranlib $BUILD_DIR/lb/lib/*.a
+
+This time 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. Under csh/tcsh you use:
 
  set IR=-I$BUILD_DIR/lb/include
  setenv CPPFLAGS "$IR $IR/libart-2.0 $IR/freetype2 $IR/libpng"
@@ -148,9 +162,13 @@ If you are running bash/sh/ash/ksh/zsh use this:
  CFLAGS=-O3
  export CPPFLAGS LDFLAGS CFLAGS
 
-And finally try building again:
+And finally try building again. We disable the python bindings because it
+seems that a fair number of people have ill configured python setups that
+would prevent rrdtool from building if they are included in their current
+state.
 
- ./configure --prefix=$INSTALL_DIR && make && make install
+ cd $BUILD_DIR/rrdtool-1.2.10
+ ./configure --prefix=$INSTALL_DIR --disable-python && make clean && make && make install
 
 Now go to I<$INSTALL_DIR>B</examples> and run them to see if your
 build has been successful.