On Fri, 02 Jan 2015 16:52:10 +0100 "Enrico Weigelt, metux IT consult" <enrico.weigelt@gr13.net> wrote: > Hi folks, > > I'm just packaging some library to various deb distros using > pbuilder + git-buildpackage. > > Unfortunately, the .so's loose the +x flag in the package > (while usual 'make install' is okay) - it seems that some of the > dh stuff drops that flag :( This is correct. Why would a .so be executable? $ find /usr/lib/x86_64-linux-gnu/ -type f -executable -name '*.so*' $ $ find /usr/lib/x86_64-linux-gnu/ -type f -executable -name '*.so' $ https://www.debian.org/doc/debian-policy/ch-files.html#s-libraries 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. A common example are the so-called "plug-ins", internal shared objects that are dynamically loaded by programs using dlopen(3). -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpznGcqghPMP.pgp
Description: OpenPGP digital signature