Florian, On Tue, Jun 8, 2010 at 3:00 PM, Jerome Renard <[email protected]> wrote: > Florian, > > On Tue, Jun 8, 2010 at 12:31 PM, Florian Forster <[email protected]> wrote: >> Hi Marc, >> >> On Tue, Jun 08, 2010 at 10:45:51AM +0200, Marc Fournier wrote: >>> A few relevant pieces below: >> > [...] > >> >> To work around these problems, do the following: >> >> - Create the required symlinks by hand: >> >> /usr/lib # ln -s libvarnish.so.1 libvarnish.so >> /usr/lib # ln -s libvarnishapi.so.1 libvarnish.so > > Confirmed, here is what I get : > > jer...@debian-collectd:~/collectd$ find /usr/lib/ -type 'l' -name > '*varnish*' -print > /usr/lib/libvarnishcompat.so.1 > /usr/lib/libvarnish.so > /usr/lib/libvarnishapi.so > /usr/lib/libvarnishapi.so.1 > /usr/lib/libvarnish.so.1 > /usr/lib/libvarnishcompat.so > >> >> - Add the .pc file to include the required libraries. Under Debian, >> edit /usr/lib/pkgconfig/varnishapi.pc so that the "Libs:" line >> reads: >> >> Libs: -L${libdir} -lvarnishapi -lvarnish -lpcre > > Actually the correct line is : > Libs: -L${libdir} -lvarnish -lvarnishcompat -lvarnishapi > > Here is the Debian version I use : > jer...@debian-collectd:~/collectd$ lsb_release -a > No LSB modules are available. > Distributor ID: Debian > Description: Debian GNU/Linux unstable (sid) > Release: unstable > Codename: sid >
I am thinking about documenting this workaround for Debian. Iwas thinking about adding a README file especially for that purpose, do you prefer a README.varnish file or a README.debian one ? -- Jérôme _______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
