Nagios plugins compile errors on OS X 10.3 Server

[Andrew Davis]

Disregard. I pulled down m4 and automake from the GNU site, compiled 
them and put /usr/local/bin into my path and all is fine.

  A. Davis
  Email:     nccomp at gmail.com

  "There is no limit to what a man can accomplish
   if he doesn't care who gets the credit." - Ronald Reagan



Andrew Davis wrote:
> I'm having some issues compiling Nagios (natively, not through 
> MacPorts, etc) on two Mac servers. One is running 10.3, the other 
> 10.4. Both are PPC. Neither can be updated to 10.5 due to third party 
> s/w constraints.
>
> On the 10.3 server, after running ./configure it seems to end okay, 
> but I see the following when running "make all":
>
>     configure: creating ./config.status
>     config.status: creating gl/Makefile
>     config.status: creating Makefile
>     config.status: creating lib/Makefile
>     config.status: creating plugins/Makefile
>     config.status: creating lib/tests/Makefile
>     config.status: creating plugins-root/Makefile
>     config.status: creating plugins-scripts/Makefile
>     config.status: creating plugins-scripts/subst
>     config.status: creating plugins-scripts/utils.pm
>     config.status: creating plugins-scripts/utils.sh
>     config.status: creating perlmods/Makefile
>     config.status: creating command.cfg
>     config.status: creating test.pl
>     config.status: creating pkg/solaris/pkginfo
>     config.status: creating po/Makefile.in
>     config.status: creating config.h
>     config.status: config.h is unchanged
>     config.status: executing depfiles commands
>     config.status: executing po-directories commands
>     config.status: creating po/POTFILES
>     config.status: creating po/Makefile
>                 --with-apt-get-command: /sw/bin/apt-get
>                   --with-ping6-command: /sbin/ping6 -n -c %d %s
>                    --with-ping-command: /sbin/ping -n -c %d %s
>                            --with-ipv6: yes
>                           --with-mysql: no
>                         --with-openssl: yes
>                          --with-gnutls: no
>                    --enable-extra-opts: no
>                            --with-perl: /usr/bin/perl
>                  --enable-perl-modules: no
>                          --with-cgiurl: /nagios/cgi-bin
>                    --with-trusted-path: /bin:/sbin:/usr/bin:/usr/sbin
>
>     /usr/local/src/nagios-plugins-1.4.13 root# make all
>     cd . && /bin/sh
>     /usr/local/src/nagios-plugins-1.4.13/build-aux/missing --run
>     autoheader
>     configure.in:3: error: Autoconf version 2.59 or higher is required
>     configure.in:3: the top level
>     autom4te: /usr/bin/gm4 failed with exit status: 1
>     autoheader: /usr/bin/autom4te failed with exit status: 1
>     make: *** [config.h.in] Error 1
>
>
> Obviously it would seem that I might need a newer version of Autoconf? 
> Any thoughts on a workaround or where I can get autoconf 2.59 or 
> higher for OS X 10.3 Server?
> -- 
>
>
>   A. Davis
>   Email:     nccomp at gmail.com
>
>   "There is no limit to what a man can accomplish
>    if he doesn't care who gets the credit." - Ronald Reagan
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090318/f84a9a8a/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
-------------- next part --------------
_______________________________________________
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