Le jeudi 05 septembre 2019 à 15:40 +0200, Rafael Laboissière a écrit : > Building the new upstream version 2.6.0 of package octave-stk triggers > loads of Lintian errors like this one: > > E: octave-stk: library-not-linked-against-libc usr/lib/x86_64-linux- > gnu/octave/packages/stk-2.6.0/x86_64-pc-linux-gnu-api- > v52/__stk_dist_pairwise__.mex > > Indeed, libc.so.* does not appear as NEEDED in the Dynamic Section of > objdump for the MEX file above: > > $ objdump -x src/__stk_dist_pairwise__.mex | grep "^ NEEDED" > NEEDED liboctinterp.so.6 > NEEDED libm.so.6 > > This is not the case for all MEX files, for instance: > > $ objdump -x src/__stk_sampling_vdc_rr2__.mex | grep "^ NEEDED" > NEEDED liboctinterp.so.6 > NEEDED libc.so.6 > > for which the Lintian error is not triggered. > > The octave-stk package works fine, because MEX files are not "shared > libraries" in the strict sense of the term. It seems like this is a > Lintian's false positive. 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. Best, ¹ https://lintian.debian.org/tags/library-not-linked-against-libc.html ² If it were underlinked, the following command would give a list of missing functions: ldd -r /usr/lib/x86_64-linux-gnu/octave/packages/stk-2.5.1/x86_64-pc-linux-gnu-api-v52/__stk_dist_pairwise__.mex -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part