[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg packaging problems

On 01/02/2015 at 10:52 AM, Enrico Weigelt, metux IT consult 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 :(

Are .so files really supposed to have +x?

On my system, the only *.so files under


which appear to have any executable bit set are ld.so, libpthread, libc,
and the many .so files from my locally-built (and not dpkg-installed)
copy of Wine. That leads me to suspect that it's intentional that .so
files are not marked executable in Debian.

According to the Debian Policy Manual section 8.1 [1], "Shared libraries
should not be installed executable, since the dynamic linker does not
require this and trying to execute a shared library usually results in a
core dump.".

Also, there appears to be a lintian tag warning against doing this [2],
which states that "Shared libraries should be mode 0644.".

Is there a particular reason why these library files need to be
executable in this particular case?

[2] https://lintian.debian.org/tags/shlib-with-executable-bit.html

   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: