Re: how to fix lintian error: library-not-linked-against-libc
* Russ Allbery <rra@debian.org> [250126 12:47]:
> In theory it would be possible to do better in Lintian by scanning the
> symbol table to see if the libc dependency is really unneeded. But doing
> that sounds at least a little annoying.
Annoying to users of lintian or annoying to implement? How so?
I thought of this solution while reading earlier in this thread, and it
seems like the "correct" solution to me. What is wrong with it?
Clearly the current state is a bug in lintian, as so many packages
override this error. And from your description, the test has a
significant purpose that is still needed in the situations it was
intended to catch, even if they are few. The lintian test simply does
not correctly identify _only_ the situations it was supposed to; it
catches many more false positives (now, due to changing programming
practices) than true positives.
...Marvin
Reply to: