compiling plugins with check_radius

[Thomas Guyot-Sionnest]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24/07/08 12:04 PM, Ford, Andy wrote:
> Trying to compile nagios-plugins-1.4.12 including check_radius.
> 
> I don't know how to get the configure script to find the radiusclient-ng
> libraries & headers.
> 
> radiusclient-ng was built with ./configure
> --prefix=/usr/local/radiusclient-ng for the sake of keeping it separate.
> 
> The configure script for nagios-plugins doesn't seem to offer an obvious
> way to point to the libraries though.
> 
> My best guess was 
> 
> ./configure --libdir=/usr/local/radiusclient-ng/lib/
> --includedir=/usr/local/radiusclient-ng/include/
> --with-trusted-path=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/radiusclien
> t-ng/sbin 

Those options are for specifying installation paths on nagios-plugins
itself. Looks like we forgot to put a --with-radius= option... Try the
following (make sure the paths are correct...):

> CFLAGS=" -I/usr/local/radiusclient-ng/include " LDFLAGS=" -L/usr/local/radiusclient-ng/lib " ./configure <your options here>

If that doesn't work I'll probably have to get my hands on a server
without radiusclient for testing...

Thomas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIiZ8/6dZ+Kt5BchYRAmJQAJwIQQZLnYLadtUrhZQWqASGr7Ge+ACbBq1h
a8bWqwFpD2NKvEF400GEZB0=
=W7in
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null