The rrdtool-1.4.3 configure script will look for and use libdbi. The ebuild doesn't handle this so you can't specify a dbi USE flag to if you need it as a dependancy. My simple patch that added '$(use_enable dbi libdbi) ' to the ebuild doesn't work because the configure script doesn't handle '--enable-libdbi', it seems to treat it as --disable-libdbi. Sigh. Looks like we need a patch to the configure.ac so it works with the standard use_enable. I'm afraid I can't do that at the moment. Can someone who knows M4/configure do the patch. Reproducible: Always Steps to Reproduce: 1. build rrdtool without libdbi installed - not linked in (ldd /usr/bin/rrdtool) 2. build rrdtool with libdbi installed - it is linked in
Created attachment 235387 [details, diff] add dbi USE flag Simple patch to add dbi FLAG and use_enable - but the configure.ac script doesn't support --enable-libdbi so that needs patching too - which I haven't done.
You just need a "--disable-libdbi" in case you don't want to build against. And it does build against without further parameter? $(use dbi || echo "--disable-libdbi") might be your man ;-)
Created attachment 251173 [details, diff] patch to add 'dbi' USE flag Included Michael's suggestion. Thanks. made 'dbi' USE flag the default so as not to break those using it who upgrade without adding the flag. Those who don't use it and don't want it are more likely to notice the new packages being installed and can remove the flag.
Fixed in 1.4.7.
