tags 317615 wontfix retitle 317615 [external] check for conflicting C++ library dependencies thanks
I thought there was some further discussion in the bug, but apparently not. > I think it would be a good idea for lintian to test for C++ ABI mixups > during the transition. As an example look at bookmarkbridge: > > % ldd /usr/bin/bookmarkbridge | grep std > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x55fe4000) > libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x5622d000) > > In general lintian could check for any occurences of two sonames of > the same library. I'm pretty sure that what you were seeing was not a binary literally linked against two different SONAMEs of a library at the same time (I'm not sure you could even convince the library and linker to do that without deep magic), but rather a binary that was linked against one C++ library and against a library that was then linked against a different one. bookmarkbridge, for instance, also links against Qt, and I bet that's where the old version was coming from for the transition. As such, finding this requires chasing transitive library dependencies, which is outside the scope of lintian (lintian only does checks contained within a single package). However, since this bug was originally reported, checklib has started doing archive-wide checks for shared library problems. This is probably best reported there. Leaving this bug open tagged wontfix as an idea seed for other projects until we can confirm that something is doing this. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
