@@ -57,7 +74,7 @@ may already be installed on your system. You have to compile copies of the other 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 +then you can either type 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 tar and make are actually GNU @@ -79,8 +96,8 @@ tar and GNU make respectively. It could be that they a
Once you have decided. Save the two locations into environment variables.
BUILD_DIR=/tmp/rrdbuild - INSTALL_DIR=/usr/local/rrdtool-1.3rc9-
If your /tmp is mounted with the option noexec (RHEL seems todo that) you have to choose + INSTALL_DIR=/usr/local/rrdtool-1.3.2 +
If your /tmp is mounted with the option noexec (RHEL seems todo that) you have to choose a different directory!
Now make sure the BUILD_DIR exists and go there:
@@ -89,9 +106,9 @@ a different directory!Lets first assume you already have all the necessary libraries pre-installed.
- wget http://oss.oetiker.ch/rrdtool/pub/rrdtool-1.3rc9.tar.gz - gunzip -c rrdtool-1.3rc9.tar.gz | tar xf - - cd rrdtool-1.3rc9 + wget http://oss.oetiker.ch/rrdtool/pub/rrdtool-1.3.2.tar.gz + gunzip -c rrdtool-1.3.2.tar.gz | tar xf - + cd rrdtool-1.3.2 ./configure --prefix=$INSTALL_DIR && make && make installOk, this was very optimistic. This try will probably have ended with configure complaining about several missing libraries.
@@ -103,7 +120,9 @@ pre-installed. you may get away with installing the missing packages. When the packages are installed, run configure again and try to compile again. Below you find some hints on getting your OS ready for the rrdtool compilation. -Additions to this list are welcome.
+Additions to this list are welcome. In general rrdtool should work with the +latest versions of the libraries. The versions listed here are just what was +current when I tested this.
OpenSolaris 2008.05
@@ -111,12 +130,20 @@ hints on getting your OS ready for the rrdtool compilation.pkg install sunstudioexpress pkg install SUNWgnome-common-devel-There is a problem with cairo.pc on opensolaris. It suggests that +
There is a problem with cairo.pc on OpenSolaris. It suggests that xrender is required for compilation with cairo. This is not true and also -bad since opensolaris does not include an xrender.pc file. Use perl to +bad since OpenSolaris does not include an xrender.pc file. Use Perl to fix this:
perl -i~ -p -e 's/(Requires.*?)\s*xrender.*/$1/' /usr/lib/pkgconfig/cairo.pc+Make sure rrdtool finds your new compiler
++ export PATH=/opt/SunStudioExpress/bin+Since there does not seem to be a viable msgfmt tool on OpenSolaris (short +of installing it yourself). You have to call configure with the
++ --disable-libintl+option.
Debian / Ubuntu
@@ -141,7 +168,7 @@ flags are available: tcl - build and install tcl language bindings rrdcgi - build and install rrdcgi
After you've decided which USE flags you need, set them either in -make.conf or /etc/portage/package.use and finally run:
+make.conf or /etc/portage/package.use and finally run:# emerge -va rrdtool
Take a look at Gentoo handbook for further details on how to manage USE @@ -158,8 +185,8 @@ possible that they are pretty old and thus don't live up to our expectations, so you may want to compile their latest versions.
-
If you are working with AIX, you may find the the --disable-shared option +
If you are working with AIX, you may find the --disable-shared option will cause things to break for you. In that case you may have to install the shared libraries into the rrdtool PREFIX and work with --disable-static instead.
@@ -170,55 +197,48 @@ instead.(Better instructions for AIX welcome!)
-
In order to build the libraries you need a compiler on your system. -Unfortunately compilers are not all alike. This has an effect on the CFLAGS -you want to set. The examples below are for the popular GCC compiler suite. -If you have an other compilers here are some ides:
-- CFLAGS="-xO3 -kPIC"-
Some libraries want to know where other libraries are. For this to work, set the following environment variable
export PKG_CONFIG_PATH=${INSTALL_DIR}/lib/pkgconfig
export PATH=$INSTALL_DIR/bin:$PATH
-This relies on the presence of the pkgconfig program. Below you find instructions -on how to compile pkgconfig as well.
-Since we are compiling libraries dynamically, they must know -where to find each other. This is done by setting an appropriate LDFLAGS. -Unfortunately, the syntax again differs from system to system:
+The above relies on the presence of the pkgconfig program. Below you find instructions +on how to compile pkgconfig.
+Since we are compiling libraries dynamically, they must know where to find +each other. This is done by setting an appropriate LDFLAGS. Unfortunately, +the syntax again differs from system to system:
export LDFLAGS=-R${INSTALL_DIR}/lib
+if you are using the Sun Studio/Forte compiler, you may also want to set
++ CFLAGS="-xO3 -xcode=pic13" (SPARC) + CFLAGS="-xO3 -Kpic" (x86)
export LDFLAGS="-Wl,--rpath -Wl,${INSTALL_DIR}/lib"
-
export LDFLAGS="+b${INSTALL_DIR}/lib"
export LDFLAGS="-Wl,-blibpath:${INSTALL_DIR}/lib"
-If you have GNUmake installed and it is not called 'make', +
If you have GNU make installed and it is not called 'make', then do
export MAKE=gmake @@ -226,10 +246,9 @@ then dootherwise just do
export MAKE=make-
+
+As mentioned above, without pkgconfig the whole build process will be lots of pain and suffering, so make sure you have a copy on your system. If it is not available natively, here is how to compile it.
@@ -240,10 +259,13 @@ not available natively, here is how to compile it. ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" $MAKE $MAKE install -After installing pkgconfig in a custom directory, setting up the corresponding +environment variable will be helpful.
++ export PKG_CONFIG=$INSTALL_DIR/bin/pkg-config+
+
+Chances are very high that you already have that on your system ...
cd $BUILD_DIR @@ -253,10 +275,9 @@ not available natively, here is how to compile it. ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" --shared $MAKE $MAKE install-
+
+Libpng itself requires zlib to build, so we need to help a bit. If you already have a copy of zlib on your system (which is very likely) you can drop the settings of LDFLAGS and CPPFLAGS. Note that the backslash (\) at @@ -269,10 +290,9 @@ the end of line 4 means that line 4 and line 5 are on one line.
env CFLAGS="-O3 -fPIC" ./configure --prefix=$INSTALL_DIR $MAKE $MAKE install -+
+cd $BUILD_DIR wget http://oss.oetiker.ch/rrdtool/pub/libs/freetype-2.3.5.tar.gz @@ -285,22 +305,20 @@ the end of line 4 means that line 4 and line 5 are on one line. add the following at the start the configure line:env EGREP=egrep-
+
+cd $BUILD_DIR - wget http://oss.oetiker.ch/rrdtool/pub/libs/libxml2-sources-2.6.31.tar.gz - gunzip -c libxml2-sources-2.6.32.tar.gz | tar xf - - cd libxml2-sources-2.6.32 + wget http://oss.oetiker.ch/rrdtool/pub/libs/libxml2-2.6.32.tar.gz + gunzip -c libxml2-2.6.32.tar.gz | tar xf - + cd libxml2-2.6.32 ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" $MAKE $MAKE install-
+
+Note that fontconfig has a run time configuration file in INSTALL_DIR/etc you may want to adjust that so that fontconfig finds the fonts on your system. Run the fc-cache program to build the fontconfig cache after changing the @@ -310,13 +328,12 @@ config file.
wget http://oss.oetiker.ch/rrdtool/pub/libs/fontconfig-2.4.2.tar.gz gunzip -c fontconfig-2.4.2.tar.gz | tar xf - cd fontconfig-2.4.2 - ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" + ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" --with-freetype-config=$INSTALL_DIR/bin/freetype-config $MAKE $MAKE install -+
+cd $BUILD_DIR wget http://oss.oetiker.ch/rrdtool/pub/libs/pixman-0.10.0.tar.gz @@ -325,14 +342,13 @@ config file. ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" $MAKE $MAKE install-
+
+cd $BUILD_DIR wget http://oss.oetiker.ch/rrdtool/pub/libs/cairo-1.6.4.tar.gz - gunzip -c cairo-1.4.10.tar.gz | tar xf - + gunzip -c cairo-1.6.4.tar.gz | tar xf - cd cairo-1.4.10 ./configure --prefix=$INSTALL_DIR \ --enable-xlib=no \ @@ -341,32 +357,31 @@ config file. CFLAGS="-O3 -fPIC" $MAKE $MAKE install-
+
+cd $BUILD_DIR wget http://oss.oetiker.ch/rrdtool/pub/libs/glib-2.15.4.tar.gz - gunzip -c glib-2.12.13.tar.gz | tar xf - - cd glib-2.12.13 + gunzip -c glib-2.15.4.tar.gz | tar xf - + cd glib-2.15.4 ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" $MAKE $MAKE install-
+
+cd $BUILD_DIR - wget http://oss.oetiker.ch/rrdtool/pub/libs/pango-1.21.1.tar.gz - gunzip -c pango-1.21.1.tar.gz | tar xf - + wget http://oss.oetiker.ch/rrdtool/pub/libs/pango-1.21.1.tar.bz2 + bunzip2 -c pango-1.21.1.tar.bz2 | tar xf - cd pango-1.21.1 ./configure --prefix=$INSTALL_DIR CFLAGS="-O3 -fPIC" --without-x $MAKE $MAKE install-
+
+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 shell you @@ -376,13 +391,13 @@ 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 their current state.
- cd $BUILD_DIR/rrdtool-1.3rc9 + cd $BUILD_DIR/rrdtool-1.3.2 ./configure --prefix=$INSTALL_DIR --disable-tcl --disable-python $MAKE clean $MAKE $MAKE install-
SOLARIS HINT: if you want to build the perl module for the native perl (the -one shipping with Solaris) you will need the sun forte compiler installed on +
SOLARIS HINT: if you want to build the Perl module for the native Perl (the +one shipping with Solaris) you will need the Sun Forte compiler installed on your box or you have to hand-tune bindings/perl-shared/Makefile while building!
Now go to $INSTALL_DIR/share/rrdtool/examples/ and run them to see if @@ -391,9 +406,7 @@ your build has been successful.
Tobias Oetiker <tobi@oetiker.ch> - -
+Tobias Oetiker <tobi@oetiker.ch>