> As a result, the library gets installed to usr/lib/${DEB_HOST_MULTIARCH} > rather than usr/lib/x86_64-linux-gnu
debian/rules has ``` DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) ``` so I thought (on respective machines), {DEB_HOST_MULTIARCH} equals x86_64-linux-gnu. Not the case? On Mon, Jul 15, 2019 at 3:22 PM Sven Joachim <svenj...@gmx.de> wrote: > > On 2019-07-15 14:44 +0200, Nico Schlömer wrote: > > > Hi everyone, > > > > when upgrading gmsh to 4.4.0, I'm getting the build error > > ``` > > [...] > > dpkg-shlibdeps: error: cannot find library libgmsh.so.4.4 needed by > > debian/gmsh/usr/bin/gmsh (ELF format: 'elf64-x86-64' abi: > > '0201003e00000000'; RPATH: '') > > dpkg-shlibdeps: error: cannot continue due to the error above > > Note: libraries are not searched in other binary packages that do not > > have any shlibs or symbols file. > > To help dpkg-shlibdeps find private libraries, you might need to use -l. > > ``` > > see [1]. I'm not exactly sure why libgmsh.so.4.4 cannot be found; the > > library is linked with > > ``` > > -Wl,-soname,libgmsh.so.4.4 -o libgmsh.so.4.4.0 > > ``` > > Any hints? > > Probably that is a consequence of your commit a44d5ad253b8[1] which > removed the executable bit from debian/*.install. As a result, the > library gets installed to usr/lib/${DEB_HOST_MULTIARCH} rather than > usr/lib/x86_64-linux-gnu, and dpkg-shlibdeps will not look in such a > strange place. > > Cheers, > Sven > > > 1. > https://salsa.debian.org/science-team/gmsh/commit/a44d5ad253b874869f643a02c7d3ca4f4b6c05c0