[Bug 743484] Re: libupsclient.pc contains unresolved symbols

Fabrice Coutadeur coutadeurf at gmail.com
Tue Mar 29 19:22:01 UTC 2011


Salut Arnaud!

I was going to report the patch (that contains both .in files) to Debian
as soon as it got uploaded to Ubuntu: you've been faster!

Thanks!

Fabrice

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/743484

Title:
  libupsclient.pc contains unresolved symbols

Status in “nut” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nut

  Hi,

  While I was investigating a FTBFS in collectd:
  ...
  configure:22249: checking for upscli_connect in -lupsclient
  configure:22274: i686-linux-gnu-gcc -o conftest -Wall -g -O2 -I/build/fabrice-collectd_4.10.1-2.1build1-i386-7yH3eE/collectd-4.10.1/debian/include -DLT_LAZY_OR_NOW='RTLD_LAZY|RTLD_GLOBAL' -UCONFIGFILE -DCONFIGFILE='"/etc/collectd/collectd.conf"'   -Wl,-Bsymbolic-functions @LIBSSL_LDFLAGS@ -L/lib -lupsclient   conftest.c -lupsclient  -ldl  >&5
  i686-linux-gnu-gcc: @LIBSSL_LDFLAGS@: No such file or directory
  I discovered that this reference to LIBSSL_LDFLAGS comes from libupsclient.pc.

  As you can see in actual .pc file, this reference has not been resolved at compile time (content of more /usr/lib/pkgconfig/libupsclient.pc in a natty schroot):
  prefix=/usr
  exec_prefix=/
  libdir=/lib
  includedir=/usr/include
  sysconfdir=/etc/nut
  statepath=/var/run/nut
  nutuser=nut

  Name: libupsclient
  Description: UPS monitoring with Network UPS Tools
  Version: 2.6.0
  Libs: -L${libdir} -lupsclient @LIBSSL_LDFLAGS@
  Cflags: -I${includedir} 

  This is because configure script and all makefile.in has been updated to use and substitute LIBSSL_LIBS instead of LIBSSL_LDFLAGS, but libupsclient.pc.in has not been updated.
  By replacing LIBSSL_LDFLAGS with LIBSSL_LIBS in .in files, the generated .pc file is correct.

  Thanks,
  Fabrice



More information about the Ubuntu-sponsors mailing list