[opensuse-packaging] -rpath /usr/lib64/modules
HI! I'm still trying to get this to build: https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap:... Although I set ./configure --libexecdir=/usr/lib64 for some reason the build log shows that the OpenLDAP standard backend and overlay modules get installed into ${RPM_BUILD_ROOT}/usr/lib64/modules instead of ${RPM_BUILD_ROOT}/usr/lib64/openldap. Is /usr/lib64/modules coming from some magic macro? Any hint is appreciated. Ciao, Michael.
On Tue 09 Dec 2014 09:41:02 PM CST, Michael Ströder wrote:
HI!
I'm still trying to get this to build:
https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap:...
Although I set ./configure --libexecdir=/usr/lib64 for some reason the build log shows that the OpenLDAP standard backend and overlay modules get installed into ${RPM_BUILD_ROOT}/usr/lib64/modules instead of ${RPM_BUILD_ROOT}/usr/lib64/openldap.
Is /usr/lib64/modules coming from some magic macro?
Any hint is appreciated.
Ciao, Michael.
Hi According to the 'official' version developed at; https://build.opensuse.org/package/view_file/network:ldap/openldap2/openldap... It should be; --libexecdir=/usr/lib/openldap -- Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890) SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default up 7 days 2:09, 5 users, load average: 0.16, 0.18, 0.15 CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Malcolm wrote:
On Tue 09 Dec 2014 09:41:02 PM CST, Michael Ströder wrote:
I'm still trying to get this to build:
https://build.opensuse.org/package/show/home:stroeder:branches:network:ldap:...
Although I set ./configure --libexecdir=/usr/lib64 for some reason the build log shows that the OpenLDAP standard backend and overlay modules get installed into ${RPM_BUILD_ROOT}/usr/lib64/modules instead of ${RPM_BUILD_ROOT}/usr/lib64/openldap.
Is /usr/lib64/modules coming from some magic macro?
Any hint is appreciated.
According to the 'official' version developed at; https://build.opensuse.org/package/view_file/network:ldap/openldap2/openldap...
It should be;
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms? I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/ Ciao, Michael.
Michael Ströder <michael@stroeder.com> writes:
Malcolm wrote:
According to the 'official' version developed at; https://build.opensuse.org/package/view_file/network:ldap/openldap2/openldap...
It should be;
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
Package-private executables are not biarch, thus go below /usr/lib (written as %{_libexecdir}).
I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}). Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Andreas Schwab wrote:
Michael Ströder <michael@stroeder.com> writes:
Malcolm wrote:
According to the 'official' version developed at; https://build.opensuse.org/package/view_file/network:ldap/openldap2/openldap...
It should be;
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
Package-private executables are not biarch, thus go below /usr/lib (written as %{_libexecdir}).
I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}).
OpenLDAP's backend and overlay modules are loadable modules (run-time configuration) and thus should go into /usr/lib64/openldap. Right? But does anybody have a hint which macro brings /usr/lib64/modules into the game? Ciao, Michael.
On Wednesday 2014-12-10 09:18, Andreas Schwab wrote:
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
Package-private executables are not biarch, thus go below /usr/lib (written as %{_libexecdir}).
I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}).
openldap's modules are not meant to be loaded by more than one arch, namely the arch that openldap is installed for. So it appears legitimate for openldap not to put it in libdir. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Jan Engelhardt <jengelh@inai.de> writes:
On Wednesday 2014-12-10 09:18, Andreas Schwab wrote:
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
Package-private executables are not biarch, thus go below /usr/lib (written as %{_libexecdir}).
I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}).
openldap's modules are not meant to be loaded by more than one arch, namely the arch that openldap is installed for. So it appears legitimate for openldap not to put it in libdir.
It doesn't make sense to put a loadable module under libexecdir. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Andreas Schwab wrote:
Jan Engelhardt <jengelh@inai.de> writes:
On Wednesday 2014-12-10 09:18, Andreas Schwab wrote:
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
Package-private executables are not biarch, thus go below /usr/lib (written as %{_libexecdir}).
I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}).
openldap's modules are not meant to be loaded by more than one arch, namely the arch that openldap is installed for. So it appears legitimate for openldap not to put it in libdir.
It doesn't make sense to put a loadable module under libexecdir.
This whole discussion is meaningless unless I understand where the part "/modules" in /usr/lib64/modules automagically comes from. Ciao, Michael.
Michael Ströder <michael@stroeder.com> writes:
This whole discussion is meaningless unless I understand where the part "/modules" in /usr/lib64/modules automagically comes from.
Have you tried grep yet? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Andreas Schwab wrote:
Michael Ströder <michael@stroeder.com> writes:
This whole discussion is meaningless unless I understand where the part "/modules" in /usr/lib64/modules automagically comes from.
Have you tried grep yet?
Hmmpf, yes, grep. I've looked into the .spec file. But not grep -r. It seems the culprit was some patch file messing around with autoconf files. Ciao, Michael.
Jan Engelhardt wrote:
On Wednesday 2014-12-10 09:18, Andreas Schwab wrote:
--libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
Package-private executables are not biarch, thus go below /usr/lib (written as %{_libexecdir}).
I have some doubts. E.g. authorative DNS server package pdns places backend modules in /usr/lib64/pdns/
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}).
openldap's modules are not meant to be loaded by more than one arch, namely the arch that openldap is installed for. So it appears legitimate for openldap not to put it in libdir.
Jan, it's inspired by package apache2 where loadable Apache modules reside in /usr/lib64/apache2/. Ciao, Michael.
On Wednesday 2014-12-10 13:33, Michael Ströder wrote:
Loadable modules are biarch, thus go below /usr/lib64 (written as %{_libdir}).
openldap's modules are not meant to be loaded by more than one arch, namely the arch that openldap is installed for. So it appears legitimate for openldap not to put it in libdir.
Jan, it's inspired by package apache2 where loadable Apache modules reside in /usr/lib64/apache2/.
So what? As I have tried to show, there is no right or wrong when it comes to the location of plugins, there are only _preferences_ and the requirement being that two different plugin formats (if such a situation can even occur) cannot live at the same location for obvious reasons. automake prefers to reject combining (pkg)libexec_ with _LTLIBRARIES for example, which is why a most plugins end up in /usr/lib64. openldap does not use automake but that does not mean it's wrong. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hello, On Dec 10 00:05 Michael Ströder wrote (excerpt):
Malcolm wrote:
It should be; --libexecdir=/usr/lib/openldap
Is that really still the way to go on 64-bit platforms?
See https://en.opensuse.org/openSUSE:Specfile_guidelines#Libexecdir FYI: Regarding executables versus libraries and 'lib' versus 'lib64' see https://bugzilla.opensuse.org/show_bug.cgi?id=676897 https://bugzilla.opensuse.org/show_bug.cgi?id=575544#c2 This bugzilla comment (dated 2010-08-17) might be (still?) interesting: https://bugzilla.opensuse.org/show_bug.cgi?id=575544#c32 " %_libdir and %_libexecdir ... are the same on SUSE " I don't know if %_libdir and %_libexecdir are still same on openSUSE. But https://en.opensuse.org/openSUSE:Specfile_guidelines#Libexecdir " Libexecdir ... is redefined to /usr/lib on openSUSE systems " seems to indicate that nowadays (if yes since when?) %_libexecdir is /usr/lib regardless of the architecture. Kind Regards Johannes Meixner -- SUSE LINUX GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 21284 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
Johannes Meixner <jsmeix@suse.de> writes:
But https://en.opensuse.org/openSUSE:Specfile_guidelines#Libexecdir " Libexecdir ... is redefined to /usr/lib on openSUSE systems " seems to indicate that nowadays (if yes since when?)
Since always.
%_libexecdir is /usr/lib regardless of the architecture.
Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (5)
-
Andreas Schwab -
Jan Engelhardt -
Johannes Meixner -
Malcolm -
Michael Ströder