In the process of preparing a new oprofile package with a fix for #537744, I have encountered a peculiar situation. The fix recommended by the submitter is to link statically against /usr/lib/libbfd.a, rather than dynaimcally against -lbfd. However, doing that results in the following lintian error: E: oprofile: shlib-with-non-pic-code usr/lib/oprofile/libopagent.so.1.0.0 Since the library is installed under /usr/lib/oprofile, I am wondering if the following statement from policy applies: Shared object files (often .so files) that are not public libraries, that is, they are not meant to be linked to by third party executables (binaries of other packages), should be installed in subdirectories of the /usr/lib directory. Such files are exempt from the rules that govern ordinary shared libraries, except that they must not be installed executable and should be stripped. [0] Does that mean that I am permitted to override the lintian error? Regards, -Roberto [0] http://www.debian.org/doc/debian-policy/ch-files.html#s-libraries -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature