Re: dpkg packaging problems
On Fri, 2015-01-02 at 18:16 +0100, Enrico Weigelt, metux IT consult wrote: > On 02.01.2015 17:08, Martin Pitt wrote: > > Hi, > > > Yes, man dh_fixperms. Shared libraries don't need to and should not be > > executable. > > Oh, wasn't aware of that. Just used to that as gcc sets that flag. > Is it a bug in gcc, or are there platforms where +x is required ? ld sets the flag, and I suspect this is because it can't tell the difference between a shared library and a PIE. A shared library may work as a executable anyway, e.g.: $ /lib/i386-linux-gnu/libc.so.6 GNU C Library (Debian GLIBC 2.19-13) stable release version 2.19, by Roland McGrath et al. Copyright (C) 2014 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [...] Ben. -- Ben Hutchings Theory and practice are closer in theory than in practice. - John Levine, moderator of comp.compilers signature.asc Description: This is a digitally signed message part -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: dpkg packaging problems
On Fri, Jan 02, 2015 at 06:16:17PM +0100, Enrico Weigelt, metux IT consult wrote: > On 02.01.2015 17:08, Martin Pitt wrote: > > Yes, man dh_fixperms. Shared libraries don't need to and should not be > > executable. > > Oh, wasn't aware of that. Just used to that as gcc sets that flag. > Is it a bug in gcc, or are there platforms where +x is required ? https://unix.stackexchange.com/questions/40587/why-are-shared-libraries-executable reports it as being necessary on HP-UX. It's indeed not needed on Linux except for the odd special case, though. -- Colin Watson [cjwat...@ubuntu.com] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: dpkg packaging problems
On 02.01.2015 17:08, Martin Pitt wrote: Hi, > Yes, man dh_fixperms. Shared libraries don't need to and should not be > executable. Oh, wasn't aware of that. Just used to that as gcc sets that flag. Is it a bug in gcc, or are there platforms where +x is required ? cu -- Enrico Weigelt, metux IT consulting +49-151-27565287 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: dpkg packaging problems
Hello Enrico, Enrico Weigelt, metux IT consult [2015-01-02 16:52 +0100]: > 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 :( Yes, man dh_fixperms. Shared libraries don't need to and should not be executable. If you have a corner case where that's desirable, use -X to exclude those from permission fixes. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
dpkg packaging problems
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 :( maybe some of you guys might have an idea ? See: https://github.com/metux/fskit/tree/jessie/master https://github.com/metux/fskit/tree/trusty/master the build process is driven by: https://github.com/metux/packaging cu -- Enrico Weigelt, metux IT consulting +49-151-27565287 -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss