Package: lintian Version: 2.112.21 Hi. Lintian complains -- https://lintian.debian.org/sources/libidn -- like this on libidn: libidn-dev_1.38-4_amd64.deb (main) E no-code-sections usr/lib/x86_64-linux-gnu/libidn.a (rfc3454.o u8- uctomb.o unistd.o) As far as I know, it is perfectly fine for object files to not contain code, it happens for a C source file that looks like this: const char *some_public_variable = "foo"; I think this lintian check was intended to catch some other problem, from https://lintian.debian.org/tags/no-code-sections?version=2.112.18 "It happens when shared objects are built with -flto=auto but without - ffat-lto-objects. dh_strip strips the LTO sections but may leave the static library without any usable code." Reading https://bugs.debian.org/977596 leads me to the same conclusion, it seems to be about archives and not object files. I think that either the check should be improved what was actually intended here, and not catch an example like the one above, or this to not be treated as an 'E'rror. What do you think? /Simon
Attachment:
signature.asc
Description: This is a digitally signed message part