[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RFH: problems building against libradius1-dev with libtool-aware packages?

hey folks,

the latest upstream version of nagios-plugins has incorporated libtool
into the build process, and no longer successfully builds in a pbuilder
chroot with the following error:

/bin/sh ../libtool --tag=CC --mode=link gcc -Wall -g -O2  -L. -o check_radius  check_radius.o netutils.o utils.o ../lib/libnagiosplug.a ../lib/libcoreutils.a  -lnsl -lresolv -lradiusclient -lssl -lcrypto
gcc -Wall -g -O2 -o check_radius check_radius.o netutils.o utils.o  -L/home/sean/nagiosplug/plugins ../lib/libnagiosplug.a ../lib/libcoreutils.a -lresolv /usr/lib/gcc/i486-linux-gnu/4.0.2/../../..//.libs/libradiusclient.so -lcrypt -lnsl -lssl -lcrypto -Wl,--rpath -Wl,/usr/lib/gcc/i486-linux-gnu/4.0.2/../../..//.libs
gcc: /usr/lib/gcc/i486-linux-gnu/4.0.2/../../..//.libs/libradiusclient.so: No such file or directory
make[1]: *** [check_radius] Error 1
make[1]: Leaving directory `/home/sean/nagiosplug/plugins'
make: *** [all-recursive] Error 1

now, i don't know libtool very well/at all, but it seems the problem is being caused by
the .la file shipped with libradius1-dev in /usr/lib/libradiusclient.la.  specifically,
the following lines:

	# Is this an already installed library?

um, shouldn't that be "yes"?  i can verify that changing it fixes my compilation problem.
so my question to anyone with more libtool experience:

- am i correct in thinking this is a bug in libradius1-dev?
- is there anything i can do to work around this bug?
- or, if i'm incorrect in thinking this is a bug, what are nagios-plugins doing wrong?



Attachment: signature.asc
Description: Digital signature

Reply to: