GNOME Bugzilla – Bug 731457
configure: connman backend unnecessarily requires 'connman.pc' that breaks multilib building
Last modified: 2014-06-29 11:36:51 UTC
configure.ac states: if test "x$with_context_manager" = "xconnman"; then PKG_CHECK_MODULES(CONNMAN, connman >= 0.80) fi While at a first glance there's nothing immediately wrong with this, if you read connman.pc you'd notice that this file is meant to be used when building connman plugins. For this reason, it is installed in arch-specific pkg-config dir ($libdir/pkgconfig). Since connman can use plugins built for a single ABI only, on multilib systems connman.pc lands only in lib64 or the equivalent. The gupnp connman code uses only connman's dbus interface, and therefore is not interested in plugin building details. Therefore multilib build of gupnp could use connman backend on every ABI. However, since connman.pc is installed for native ABI only, the configure check fails and prevents e.g. 32-bit gupnp from using connman. Please consider removing the check or replacing it with something less fragile. I will also report a bug to connman upstream suggesting that the .pc file is misleading.
connman bugreport: https://01.org/jira/browse/CM-658
Created attachment 279524 [details] [review] Do not check for connman.pc Signed-off-by: Jens Georg <mail@jensge.org>
Attachment 279524 [details] pushed as e7a284d - Do not check for connman.pc