building of k debian package (jessie) sets LIBDIR like this:
DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) LIBDIR ?= lib/$(DEB_HOST_MULTIARCH)
if the package is build on amd64 architecture, LIBDIR becomes lib/x86_64-linux-gnu and on i386 architecture lib/i386-linux-gnu.
however, when the package is then installed on some host, how can the loadpath for the modules be figured automatically out? dpkg-architecture command cannot be used, because it is not installed unless the host is used for software development.
i have tried 'uname -m', but sometimes on i386 arch, it gives i386 and and sometimes i686.
-- juha
Hello,
On 11/05/15 13:02, Juha Heinanen wrote:
building of k debian package (jessie) sets LIBDIR like this:
DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) LIBDIR ?= lib/$(DEB_HOST_MULTIARCH)
if the package is build on amd64 architecture, LIBDIR becomes lib/x86_64-linux-gnu and on i386 architecture lib/i386-linux-gnu.
however, when the package is then installed on some host, how can the loadpath for the modules be figured automatically out? dpkg-architecture command cannot be used, because it is not installed unless the host is used for software development.
i have tried 'uname -m', but sometimes on i386 arch, it gives i386 and and sometimes i686.
'kamailio -I' (uppercase i) is printing several details, including the default path to modules. Maybe that is sufficient for what you need or you can do some shell scripting to extract only the modules path.
Cheers, Daniel
Daniel-Constantin Mierla writes:
'kamailio -I' (uppercase i) is printing several details, including the default path to modules. Maybe that is sufficient for what you need or you can do some shell scripting to extract only the modules path.
i tried that and got:
Default paths to modules: /usr/lib64/sip-proxy/modules
which is incorrect. on this host /usr/lib64 does not exist and modules are installed in
/usr/lib/x86_64-linux-gnu/sip-proxy
looks like i just need to dig via shell commands in init script where the libs are actually installed and then patch the config file accordingly.
-- juha
On 12/05/15 10:39, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
'kamailio -I' (uppercase i) is printing several details, including the default path to modules. Maybe that is sufficient for what you need or you can do some shell scripting to extract only the modules path.
i tried that and got:
Default paths to modules: /usr/lib64/sip-proxy/modules
which is incorrect. on this host /usr/lib64 does not exist and modules are installed in
/usr/lib/x86_64-linux-gnu/sip-proxy
looks like i just need to dig via shell commands in init script where the libs are actually installed and then patch the config file accordingly.
Then setting the default path to modules is broken somehow -- it needs to point where the modules are deployed by installation. Once I get some time, I will see if deb building is not setting some Makefile vars or the Makefile is using the wrong vars.
Cheers, Daniel
-
Daniel-Constantin Mierla -
Juha Heinanen