Compiling nagios-plugins-1.4.9 for Solaris 10

[Thomas Guyot-Sionnest]

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

On 26/09/07 09:11 PM, Tony O'Shea wrote:
> Hi all,

Hi,

First of all you should avoid using the Reply button to compose a new
message. This breaks threading and there's change many people won't ever
look at your post because it's hidden behind an unrelated one.

I'm a Nagios-plugins developer but I'm not very experienced with linking
issues. Ideally you should subscribe to Nagiosplug-devel and repost here.

> I hope that you can help me, I am having problems compiling
> nagios-plugins-1.4.9 for Solaris 10, below is the PATH & LD_LIBRARY_PATH
> setup. 

I compared what you have with my Solaris 10 box and I can't find
anything wrong... My build has SSL support.

I guess you installed OpenSSL from the Solaris 10 package (if no can you
please give more details?)

Also if you have autoconf/gen/make, gettext, libtool and GNU m4 (not the
m4 that comes with Solaris) already installed you may try the following
(from the Nagios-plugins directory):

$ tools/distclean
$ tools/setup

Then your normal configure/make. If it fails don't bother installing the
required stuff; you might get more help in the Nagiosplug-devel mailing
list.

Thomas

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

iD8DBQFG+6J86dZ+Kt5BchYRAmzmAKC8HlEH2q2pqEwil5OozQvQJAZisQCdFIQd
GqrrqdabQH0McP3c1ziGeXQ=
=QdBC
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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