On Sat, Mar 04, 2006 at 08:16:22PM +0100, Robert Jordens wrote: > Could you trigger a binNMU of liblrdf on all arches? It is build against > libssl 0.9.7 (caused by libraptor pulling in that dependency).
> Having part of the libraries link against libssl 0.9.7 and others > against 0.9.8 causes funny stuff like this: Uh, a binNMU will take care of this part: > /usr/bin/ld: warning: libssl.so.0.9.7, needed by /usr/lib/liblrdf.so, may > conflict with libssl.so.0.9.8 > /usr/bin/ld: warning: libcrypto.so.0.9.7, needed by /usr/lib/liblrdf.so, may > conflict with libcrypto.so.0.9.8 But not this part: > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > /usr/lib/libraptor.so: undefined reference to [EMAIL PROTECTED]' > collect2: ld returned 1 exit status This looks like a bug either in libcurl3, or in the maintainer's build of libraptor1 on his system -- some version of libcurl3 defined these versioned symbols, but the current Debian package does not, which means the ABI of the libcurl3 used to build libraptor1 does not match the one in the archive. That's the only reason that you're getting link errors. A binNMU of liblrdf *should* be done, but the build will just fail with this same error. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
