X-Git-Url: https://git.tokkee.org/?a=blobdiff_plain;f=doc%2Frrdbuild.html;h=f7585a6623ef4a63bb589ee651baa29055a577d0;hb=77bd6159687918e59dd3bc5ae7f7c337a8ed9277;hp=c003c105f30d5a1cda1e673259dcca0f07026873;hpb=bb80fbeb0fc8a57a7c3d84eb0b6bce5aa5e37ca7;p=pkg-rrdtool.git diff --git a/doc/rrdbuild.html b/doc/rrdbuild.html index c003c10..f7585a6 100644 --- a/doc/rrdbuild.html +++ b/doc/rrdbuild.html @@ -9,8 +9,10 @@ -

+ +
+

+ + +

@@ -61,14 +67,14 @@


OVERVIEW

-

If you downloaded the source of rrdtool you have to compile it. This +

If you downloaded the source of RRDtool you have to compile it. This document will give some information on how this is done.

RRDtool relies on services of third part libraries. Some of these libraries 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 @@ -90,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.3.1
-

If your /tmp is mounted with the option noexec (RHEL seems todo that) you have to choose + INSTALL_DIR=/opt/rrdtool-1.4.7 +

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:

@@ -100,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.3.1.tar.gz
- gunzip -c rrdtool-1.3.1.tar.gz | tar xf -
- cd rrdtool-1.3.1
+ wget http://oss.oetiker.ch/rrdtool/pub/rrdtool-1.4.7.tar.gz
+ gunzip -c rrdtool-1.4.7.tar.gz | tar xf -
+ cd rrdtool-1.4.7
  ./configure --prefix=$INSTALL_DIR && make && make install

Ok, this was very optimistic. This try will probably have ended with configure complaining about several missing libraries.

@@ -113,8 +119,10 @@ pre-installed.

If your OS lets you install additional packages from a software repository, 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.

+hints on getting your OS ready for compiling RRDtool.

+

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

@@ -122,12 +130,15 @@ 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 the RRDtool build system finds your new compiler

+
+ export PATH=/opt/SunStudioExpress/bin

Debian / Ubuntu

@@ -138,10 +149,10 @@ of packages will get added through dependencies.

Gentoo

-

In Gentoo installing rrdtool is really simple you just need to emerge +

In Gentoo installing RRDtool is really simple you just need to emerge rrdtool. All dependencies will be handled automatically by the portage system. The only thing you should care about are USE flags, which allow you -fine tune features rrdtool will be built with. Currently the following USE +fine tune features RRDtool will be built with. Currently the following USE flags are available:

  doc    - install .html and .txt documentation
@@ -152,7 +163,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 @@ -170,11 +181,11 @@ expectations, so you may want to compile their latest versions.

General build tips for AIX

-

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 +shared libraries into the RRDtool PREFIX and work with --disable-static instead.

-

Another hint to get rrdtool working on AIX is to use the IBM XL C Compiler:

+

Another hint to get RRDtool working on AIX is to use the IBM XL C Compiler:

  export CC=/usr/vac/bin/cc
  export PERLCC=$CC
@@ -182,55 +193,47 @@ instead.

Build Instructions

-

In order to build rrdtool 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:

-
-
Sun Forte
- -
-
- 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
-

The above relies on the presence of the pkgconfig program. Below you find instructions +

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:

-
Solaris
+
Solaris
  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)
-
Linux
+
Linux
  export LDFLAGS="-Wl,--rpath -Wl,${INSTALL_DIR}/lib"
-
HPUX
+
HPUX
  export LDFLAGS="+b${INSTALL_DIR}/lib"
-
AIX
+
AIX
  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
@@ -251,6 +254,10 @@ 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

Building zlib

@@ -298,9 +305,9 @@ add the following at the start the configure line:

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.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
@@ -316,7 +323,7 @@ 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

@@ -336,8 +343,8 @@ config file.

  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 -
- cd cairo-1.4.10
+ gunzip -c cairo-1.6.4.tar.gz   | tar xf -
+ cd cairo-1.6.4
  ./configure --prefix=$INSTALL_DIR \
     --enable-xlib=no \
     --enable-xlib-render=no \
@@ -345,14 +352,21 @@ config file.

CFLAGS="-O3 -fPIC" $MAKE $MAKE install
+

When building on Solaris you may want todo

+
+ ./configure --prefix=$INSTALL_DIR \
+    --enable-xlib=no \
+    --enable-xlib-render=no \
+    --enable-win32=no \
+    CFLAGS="-O3 -fPIC -D_POSIX_PTHREAD_SEMANTICS"

Building Glib

  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
@@ -361,8 +375,8 @@ config file.

Building Pango

  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
@@ -376,15 +390,15 @@ files. This is done via environment variables. Depending on the shell you
 are running, the syntax for setting environment variables is different.

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 +tcl setups that would prevent RRDtool from building if they are included in their current state.

- cd $BUILD_DIR/rrdtool-1.3.1
+ cd $BUILD_DIR/rrdtool-1.4.7
  ./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 +

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!