Package: pkg-config
Version: 0.26-1
Severity: minor
In Autoconf output from PKG_CHECK_MODULES in pkg.m4, the "checking for"
message refers to the first argument of PKG_CHECK_MODULES, the variable
prefix, instead of the second argument, the module being checked for.
I've seen this result in strange output (like ALL CAPS module names) in
various packages, and now have run into it in one of mine. When
probing for the libsystemd-daemon module, one can't use a variable
prefix that matches the module name (since - isn't allowed in variable
names), so the Autoconf output is going to refer to something odd, like
SYSTEMD_DAEMON or libsystemd_daemon.
I think the status output should reference the module name being
probed for, both because it looks nicer and because, when debugging
problems, this references the actual thing being probed for on the
system, rather than an internal implementation detail.
This could be easily done by changing the line:
AC_MSG_CHECKING([for $1])
in pkg.m4 to:
AC_MSG_CHECKING([for $2])
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.11-2-amd64 (SMP w/8 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 pkg-config depends on:
ii libc6 2.17-97
ii libglib2.0-0 2.36.4-1
ii libpopt0 1.16-8
pkg-config recommends no packages.
pkg-config suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
