[Nagiosplug-help] Nagios Plugin Compilation and Solaris 10

[Keegan,Nate]

Solaris 10 update 5 x86
Nagios 3.0.6
Nagios Plugins 1.4.13, 1.4.12

I am getting an error when compiling 1.4.13 or 1.4.12 (but not 1.4.9) plugins on this platform.

First the configure:

./configure --with-openssl=/usr/local/ssl --with-snmpget-command=/usr/local/net-snmp/bin/snmpget
--with-snmpgetnext-command=/usr/local/net-snmp/bin/snmpgetnext
--with-fping-command=/usr/sbin/fping --with-ssh-command=/bin/ssh
--without-mysql --with-ldap

When I run gmake I get this:

if gcc -DLOCALEDIR=\"/usr/local/nagios/share/locale\" -DHAVE_CONFIG_H
-I. -I. -I.. -I.. -I../lib -I../gl -I../intl -I../plugins -I/usr/local/ssl/include
-I/usr/local/ssl/include -m64 -g -O2 -MT pst3-pst3.o -MD -MP -MF ".deps/pst3-pst3.Tpo" -c -o pst3-pst3.o
`test -f 'pst3.c' || echo './'`pst3.c; \
then mv -f ".deps/pst3-pst3.Tpo" ".deps/pst3-pst3.Po"; else rm -f ".deps/pst3-pst3.Tpo"; exit 1; fi
pst3.c:1: sorry, unimplemented: 64-bit mode not compiled in
gmake[2]: *** [pst3-pst3.o] Error 1
gmake[2]: Leaving directory `/usr/local/src/nagios-plugins-1.4.13/plugins-root'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/local/src/nagios-plugins-1.4.13'
gmake: *** [all] Error 2

Nothing shows up in config.log

I'm on 64-bit Solaris (isainfo -b shows 64) and I see in configure where this is being hashed out:

{ echo "$as_me:$LINENO: result: using nagios-plugins internal ps command (pst3) for solaris" >&5
echo "${ECHO_T}using nagios-plugins internal ps command (pst3) for solaris" >&6; }
        if test `isainfo -b` = 64 ; then
                PST3CFLAGS="-m64"

                { echo "$as_me:$LINENO: using 64bit pst3" >&5
echo "$as_me: using 64bit pst3" >&6;}
        else
                { echo "$as_me:$LINENO: using 32bit pst3" >&5
echo "$as_me: using 32bit pst3" >&6;}
        fi

I'm not sure where to go from here exactly. I get that it is some sort of 64-bit vs 32-bit issue but I'm not sure how to adjust for it.

I searched around Google, Nagios mailing lists, etc and only found one instance of this and that was for Solaris 8 I believe.

Same thing happens with plugins 1.4.12 and 1.4.13 so I'm guessing whatever tweak is required to remedy this would apply to either plugin tarball.