Le 14/09/2019 à 17:33, Sébastien Villemot a écrit :
According to the tag description¹, there are legitimate cases where the
library is not linked to libc, in which case lintian will still
complain. It looks like this is such a situation, because the library
is not underlinked.² So I would simply add an override.
This issue was already discussed on the old list (Pkg-octave-devel) a
long time ago (november 2015, look for "octave-stk: current status /
help needed" in the title).
The discussion resulted in the following overrides:
$ cat debian/octave-stk.lintian-overrides
# Ignore library-not-linked-against-libc warning
# since no symbol from libc is used in this mex-files:
octave-stk binary: library-not-linked-against-libc */__stk_dist_matrixx__.mex
octave-stk binary: library-not-linked-against-libc */__stk_dist_matrixy__.mex
octave-stk binary: library-not-linked-against-libc */__stk_dist_pairwise__.mex
octave-stk binary: library-not-linked-against-libc */__stk_distrib_bivnorm0_cdf__.mex
octave-stk binary: library-not-linked-against-libc */__stk_filldist_discr_mex__.mex
octave-stk binary: library-not-linked-against-libc */__stk_gpquadform_matrixx__.mex
octave-stk binary: library-not-linked-against-libc */__stk_gpquadform_matrixy__.mex
octave-stk binary: library-not-linked-against-libc */__stk_gpquadform_pairwise__.mex
octave-stk binary: library-not-linked-against-libc */__stk_mindist_mex__.mex
So, I don't understand why you still get warnings...