Package: libopenmpi-dev
Version: 3.1.0-3
Severity: normal
openmpi3's pkgconfig files contain rpaths in the Libs entries, e.g.
ompi.pc contains "-Wl,-rpath -Wl,${libdir}"
Is this deliberate? Debian best practice tells us that we shouldn't
use rpaths since they interfere with library search paths.
Client packages (e.g. petsc) pick up the openmpi configuration and add
the rpath to their libraries, e.g.
RUNPATH /usr/lib/x86_64-linux-gnu/openmpi/lib
This triggers the lintian warning "binary-or-shlib-defines-rpath",
referring to https://wiki.debian.org/RpathIssue
Should openmpi be patched for this, or is it an exception to the
general rule ? (in which case perhaps lintian should be patched to
ignore a RUNPATH with /usr/lib/*/openmpi/lib)
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libopenmpi-dev depends on:
ii libc6 2.27-3
ii libevent-2.1-6 2.1.8-stable-4
ii libevent-pthreads-2.1-6 2.1.8-stable-4
ii libhwloc-dev 1.11.10-1+b1
ii libhwloc5 1.11.10-1+b1
ii libibverbs-dev 18.0-1
ii libopenmpi3 3.1.0-3
ii openmpi-bin 3.1.0-3
ii openmpi-common 3.1.0-3
libopenmpi-dev recommends no packages.
Versions of packages libopenmpi-dev suggests:
pn openmpi-doc <none>
-- no debconf information
