Compiling Nagios 2.0b1 on Solaris 7

[Andreas Ericsson]

Erek Dyskant wrote:
> Hi All,
> 	I'm attempting to compile Nagios 2.0b1 on a somewhat geriatric Solaris
> box, and running into a compile error.  Nagios 1.2 compiles fine.
> 	I'm using gcc 3.3.2 and have tried both sun make and gnu make
> 3.80
> 	Thanks in advance for all your help.
> 
> Regards,
> Erek
> 
> In file included from ../include/nebmods.h:31,
> from broker.c:33:
> ../include/nebmodules.h:78: error: parse error before "lt_ptr"
> ../include/nebmodules.h:78: warning: no semicolon at end of struct or
> union
> ../include/nebmodules.h:79: warning: data definition has no type or
> storage class
> ../include/nebmodules.h:89: error: parse error before '}' token
> ../include/nebmodules.h:89: warning: data definition has no type or
> storage class
> In file included from broker.c:33:
> ../include/nebmods.h:51: error: parse error before '*' token
> ../include/nebmods.h:54: error: parse error before '*' token
> *** Error code 1
> make: Fatal error: Command failed for target `broker.o'
> Current working directory /opt/home2/erek/src/nagios-2.0b1/base
> *** Error code 1
> make: Fatal error: Command failed for target `all'
> 

It appears you do not have the libtool header files installed. They 
proved the lt_dlopen() and friends. Run ./configure 
--disable-event-broker. That might sort it out for you.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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