[Nagiosplug-help] Help compiling nrpe plugin on solaris 8 sunblade 100

Tony Despain tony.despain at gmail.com
Fri Feb 11 10:43:43 CET 2005

I have slowly been making progress on compiling nrpe on a solaris 8
machine.  At first it wouldn't compile so I added the gcc package
along with autoconf, automake, and make packages from
www.freesunware.com.  I have been able to run ./configure in the
nrpe-2.0 directory.  And I get a lot of yes answers when it runs and a
couple of no.

My Path is set as this:

When I run ./configure from the nrpe-2.0 directory this is the output:

bash-2.03# ./configure
checking for a BSD compatible install... ./install-sh -c
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking whether make sets ${MAKE}... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for ctype.h... yes
checking for dirent.h... yes
checking for errno.h... yes
checking for fcntl.h... yes
checking for getopt.h... no
checking for grp.h... yes
checking for inttypes.h... yes
checking for netdb.h... yes
checking for pwd.h... yes
checking for signal.h... yes
checking for stdint.h... no
checking for strings.h... yes
checking for string.h... yes
checking for syslog.h... yes
checking for unistd.h... yes
checking for arpa/inet.h... yes
checking for netinet/in.h... yes
checking for sys/types.h... yes
checking for sys/time.h... yes
checking for sys/resource.h... yes
checking for sys/wait.h... (cached) yes
checking for sys/socket.h... yes
checking for sys/stat.h... yes
checking for working const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for mode_t... yes
checking for pid_t... yes
checking for size_t... yes
checking return type of signal handlers... void
checking for uid_t in sys/types.h... yes
checking type of array argument to getgroups... gid_t
checking size of int... 4
checking size of short... 2
checking size of long... 4
checking for uint32_t... yes
checking for u_int32_t... no
checking for int32_t... yes
checking for main in -lnsl... yes
checking for socket in -lsocket... yes
checking for strdup... yes
checking for strstr... yes
checking for strtoul... yes
checking for initgroups... yes
checking for type of socket size... size_t
checking for SSL... configure: error: Cannot find ssl libraries

Then I run make -f Makefile.in and this is what it says:

bash-2.03# make -f Makefile.in
cd ./src/; make ; cd ..
make[1]: Entering directory `/home/adespain/nrpe-2.0/src'
make[1]: *** No targets specified and no makefile found.  Stop.
make[1]: Leaving directory `/home/adespain/nrpe-2.0/src'

*** Compile finished ***

If the NRPE daemon and client compiled without any errors, you
can continue with installation.  The NRPE daemon and client
binaries are located in the src/ subdirectory.

 ** If this is your monitoring host **

     - Copy the check_nrpe client to the directory that
       contains your Nagios plugins.
     - Create a command definition in your Nagios config
       file for the NRPE client.  See the README file for
       more info on doing this.

 ** If this host will be running the NRPE daemon **

     - Copy the nrpe daemon to /usr/sbin, /usr/local/nagios
       or wherever you feel it fits best.
     - Copy the sample nrpe.cfg config file to /etc,
       /usr/local/nagios or wherever you feel it fits best.
     - Modify the /etc/services file and configure NRPE to
       run under inetd, xinetd, or as a standalone daemon.
       See the README file for more info on doing this.


The line that says 

make[1]: *** No targets specified and no makefile found.  Stop.

seems to be my problem and I can't figure out why it is saying this. 
Does anyone have any experience compiling nrpe-2.0 on a solaris 8
sparc box?  I would greatly appreciate any help on this!!  Thanks in

More information about the Help mailing list