Ticket #272 (closed defect: for support check mailinglist)
rrdtool relies on libxml2, but doesn't support defining its location
| Reported by: | human | Owned by: | oetiker |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | misc | Version: | 1.4.4 |
| Keywords: | Cc: |
Description
I do my own build of libxml2, so there is no development RPM installed on my box in /usr/include, /usr/lib, etc. However, rrdtool has no option to specify where to find libxml2 (I.e., --with-xml2=/path/to/xml2) option in configure. This makes it unusable for my case (and I'm sure I'm not the only one) without hacking configure.



There is more to linking a library than knowing its location ... this is why most tools use pkg-config to find their libraries. If you include your alternate location in the pkg-config search path (as you are told by the configure script when it does not find a library) then things will go right smooth ... another option is to set the CPPFLAGS and LDFLAGS environment variables prior to calling configure ... again your libraries will be found even in non standard locations ...
also you may want to peak at http://oss.oetiker.ch/rrdtool/doc/rrdbuild.en.html for some compilation hints ...
hth tobi