On Wed, 16 Aug 2006, Will McDonald wrote: > On 16/08/06, dennis <dennis at bulacan.gov.ph> wrote: > > > > hi to all, > > > > im currently installing rrdtool-1.2.15 with my box CentOS 4.3 > > final ,before i installed rrdtools there 2 files suggested need to > > installed the FreeType > > Is there a specific reason for not using the RPMForge packaged > rrdtool? > > [root at devmon1 ~]# rpm -qa | grep rrd > rrdtool-1.2.13-1.el4.rf > perl-rrdtool-1.2.13-1.el4.rf Also, on Wed, 16 Aug 2006, Jim Perrin wrote: > It's far better to stick with rpms on an rpm based system. This way > all the other software knows about each other via the rpm database, > and you don't run into missing dependencies, version conflicts, and > other issues that like to creep up. To my mind, the advice given by Will and Jim is a two-edged sword: * Sure, using rpms on rpm-based systems is the surest path to stability, success, long uptimes, and Johnny's new pony :-) * It also sounds to me, however inadvertently, like "don't worry your little self about it; let the experts do the heavy lifting." In this case, the OP provided what seems to be the relevent console output for troubleshooting. In particular, the configure script couldn't find header files for libart and freetype: > checking for art_vpath_add_point in -lart_lgpl_2... yes > checking libart_lgpl/libart.h usability... no > checking libart_lgpl/libart.h presence... no > checking for libart_lgpl/libart.h... no > [....] > checking for FT_Init_FreeType in -lfreetype... yes > checking ft2build.h usability... no > checking ft2build.h presence... no > checking for ft2build.h... no A simple pair of yum queries provide the likely answer. yum whatprovides ft2build.h yum whatprovides libart.h You'll see that those files are provided by a couple development packages: freetype-devel libart_lgpl-devel Installing those will probably solve the problem of compiling rrdtool. Not that using a solid rpm from a good repository isn't good advice... -- Paul Heinlein <> heinlein at madboa.com <> www.madboa.com