Hi List, here is the error-message for compilation of "nrpe.c" on superdome with hpux 11.31 (version 3).
---schnipp--- supderdome:/home/nagios/nrpe-2.12> make all cd ./src/; make ; cd .. cc -g -I/usr/include/openssl -I/usr/include -DHAVE_CONFIG_H -c ./snprintf.c (Bundled) cc: warning 922: "-g" is unsupported in the bundled compiler, ignored. "./snprintf.c", line 273: warning #2068-D: integer conversion resulted in a change of sign size_t ret = -1; ^ cc -g -I/usr/include/openssl -I/usr/include -DHAVE_CONFIG_H -o nrpe nrpe.c utils.c -L/usr/local/lib/hpux32 -lssl -lcrypto -lnsl -lwrap ./snprintf.o (Bundled) cc: warning 922: "-g" is unsupported in the bundled compiler, ignored. nrpe.c: "nrpe.c", line 617: error #2020: identifier "LOG_AUTHPRIV" is undefined log_facility=LOG_AUTHPRIV; ^ "nrpe.c", line 619: error #2020: identifier "LOG_FTP" is undefined log_facility=LOG_FTP; ^ "nrpe.c", line 852: warning #2167-D: argument of type "socklen_t *" is incompatible with parameter of type "int *" rc=getpeername(new_sd,&addr,&addrlen); ^ "nrpe.c", line 865: warning #4232-D: conversion from "struct sockaddr *" to a more strictly aligned type "struct sockaddr_in *" may cause misaligned access nptr=(struct sockaddr_in *)&addr; ^ 2 errors detected in the compilation of "nrpe.c". utils.c: *** Error exit code 2 Stop. *** Error exit code 1 Stop. ---schnapp--- Is there some helps? Thanks a lot! NSCA 2.7.2 and Nagios-plugins 1.4.11 will works fine on the same maschine, with no errors! Detlef ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Nagios-users mailing list Nagios-users@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