Package: pkgconf
Version: 0.9.5-3
Severity: normal
"pkgconf --libs foo" only strips "-L/usr/lib" from its output, but not the
multiarch "-L/usr/lib/x86_64-linux-gnu" (as is done by pkg-config).
Example /usr/lib/x86_64-linux-gnu/pkgconfig/x264.pc
--- snip ---
prefix=/usr
exec_prefix=${prefix}
libdir=/usr/lib/x86_64-linux-gnu
includedir=${prefix}/include
Name: x264
Description: H.264 (MPEG4 AVC) encoder library
Version: 0.142.2389 956c8d8
Libs: -L/usr/lib/x86_64-linux-gnu -lx264
Libs.private: -lpthread -lm -ldl
Cflags: -I${prefix}/include
--- snip ---
$ pkgconf --libs x264
-L/usr/lib/x86_64-linux-gnu -lx264
$ pkg-config --libs x264
-lx264
This causes strange FTBFS when privately (i.e. not on a buildd) building a
multiarch package with library libfoo which is already installed (in another
version). If the linking of any shared library or executable in the package
uses another library libbar with "-L/usr/lib/x86_64-linux-gnu" in its pkg-
config Libs variable, the linker will prefer
the installed libfoo over the just built one.
pkgconf eliminates just a single system lib directory, but pkg-config
eliminates any directory in the search path for system libs. Indeed, in Debian
pkg-config is configured with /lib:/lib32:/usr/lib:/usr/lib/x86_64-linux-
gnu:/usr/lib32.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.6 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pkgconf depends on:
ii libc6 2.18-4
pkgconf recommends no packages.
pkgconf suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
