Hi Marc, On Tue, Jun 08, 2010 at 03:08:22PM +0200, Marc Fournier wrote: > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libvarnishapi.so: > undefined reference to `VRE_compile' > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libvarnishapi.so: > undefined reference to `VRE_exec'
this looks precisely like the problem on Debian. “VRE_exec” is available from "libvarnish", so the library is missing that dependency. > /usr/lib64/libvarnishapi.so: > libc.so.6 => /lib64/libc.so.6 (0x0000003ebb200000) > /lib64/ld-linux-x86-64.so.2 (0x0000003ebae00000) As I though: "libvarnishapi" is not linked against "libvarnish". > As debian squeeze ships varnish 2.1 too, I'm wondering if the problem > wouldn't be in varnish 2.1 itself, not in the way the distros package > varnish ? Yeah, I just confirmed that by looking at the current Varnish SVN trunk. > > - Create the required symlinks by hand: > > > > /usr/lib # ln -s libvarnish.so.1 libvarnish.so > > /usr/lib # ln -s libvarnishapi.so.1 libvarnish.so > > You probably ment: > /usr/lib # ln -s libvarnishapi.so.1 libvarnishapi.so Yeah, that's a typo. Sorry. > I suppose this must also be followed by a "ldconfig" run ? Worked for me without; YMMV. > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../lib64/libvarnish.so: > undefined reference to `strlcpy' That's new. I thought the GNU libc did implement "strlcpy", too..? > readelf shows that /usr/lib/libvarnish.so has a reference to strlcpy > but /usr/lib/libvarnishapi.so doesn't. Maybe adding -lvarnish finally > isn't a good idea ? "libvarnish" is needed for the "VRE_exec" and "VRE_compile" symbols, so you can't just leave that away. Regards, —octo -- Florian octo Forster Hacker in training GnuPG: 0x91523C3D http://verplant.org/
signature.asc
Description: Digital signature
_______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
