On Aug 7, 2012, at 10:14 AM, Elan Ruusamäe wrote:
> On 07.08.2012 16:48, Caleb Maclennan wrote:
>>> mount: error while loading shared libraries: libselinux.so.1: cannot open
>>> shared object file:
>>> > No such file or directory
>> Is selinux currently required for all systems? If so why do no
>> packages trigger it as a dependency? If not, why does mount want to
>> see it?
>>
> most common case:
>
> binary that depends on library is not having +x bit set in $RPM_BUILD_ROOT
>
> typical cause: lame cmake based build systems do "make install" which
> installs files with 644 permissions
>
> simple fix:
> chmod +x $RPM_BUILD_ROOT/path/to/your/binary
>
There's RPM automation available (if you wish).
Write a script that walks $RPM_BUILD_ROOT and does chmod +x. Use
patterns and directory paths to avoid false positive side effects.
Add the script to macros to be run at end of %install before
dependencies are extracted.
Its rather astonishing that years and years later that missing package
dependencies due to
non-executable bits on ELF libraries needs to be discussed.
And yes: Fix the package(s) *.spec recipes if you wish instead of automating
"chmod +x …" in RPM.
73 de Jeff
> --
> glen
>
> _______________________________________________
> pld-devel-en mailing list
> [email protected]
> http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
_______________________________________________
pld-devel-en mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
