Hello,
iirc this was at some point discussed, however, I want to go through it again.
Many x86_64 distros expect libraries to be placed under a lib64 directory. For example the RPM spec file language returns /usr/lib64 for %{_libdir} variable.
In the master branch I committed a patch that does this detection.
As I saw some people saying that 'lib' should be the default also for x86_64, my question is then what do you think we should use?
Using 'lib' will definitely make building rpms fail unless we do a patch specific for these distros.
Cheers, Daniel
If you are unsure which way is better, my recommendation would be follow the Linux Standard Base (LSB). IIRC it recommends using lib64 in this case.
-Jan
On Thu, Mar 31, 2011 at 7:07 AM, Daniel-Constantin Mierla miconda@gmail.com wrote:
Hello,
iirc this was at some point discussed, however, I want to go through it again.
Many x86_64 distros expect libraries to be placed under a lib64 directory. For example the RPM spec file language returns /usr/lib64 for %{_libdir} variable.
In the master branch I committed a patch that does this detection.
As I saw some people saying that 'lib' should be the default also for x86_64, my question is then what do you think we should use?
Using 'lib' will definitely make building rpms fail unless we do a patch specific for these distros.
Cheers, Daniel
-- Daniel-Constantin Mierla http://www.asipto.com
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Daniel-Constantin Mierla wrote:
iirc this was at some point discussed, however, I want to go through it again.
Many x86_64 distros expect libraries to be placed under a lib64 directory. For example the RPM spec file language returns /usr/lib64 for %{_libdir} variable.
In the master branch I committed a patch that does this detection.
As I saw some people saying that 'lib' should be the default also for x86_64, my question is then what do you think we should use?
Using 'lib' will definitely make building rpms fail unless we do a patch specific for these distros.
Since the libraries are actual .so files for 64bit in this case, it would sound logical to put them into lib64. Not least so that you can also have a 32-bit version on the side (dunno what for but one never knows).
To make the 32/64 bit transition transparent, would it be possible to default the loadpath to the correct directory, ie., "/usr/lib/kamailio/modules:/usr/lib/kamailio/modules_k" on 32 bit and "/usr/lib64/kamailio/modules:/usr/lib64/kamailio/modules_k" on 64 bit? This is assuming the colon semantics actually works which it didn't in my experiments.
Regards, Martin
-
Daniel-Constantin Mierla -
Jan Janak -
Martin Hoffmann