Nagios 3 statusmap.cgi on CentOS 5.1 i386

[John Duraisw]

Check whether you have gd-devel and libpng-devel installed. If not install
it and recompile it.

[root at web sbin]# yum list installed | grep gd-devel
gd-devel.i386                            2.0.33-9.4.el5_1.1     installed
[root at web sbin]# yum list installed | grep libpng-devel
libpng-devel.i386                        2:1.2.10-7.1.el5_0.1   installed

Thanks,

-john




On Thu, Mar 13, 2008 at 7:18 PM, Joey K. <pguser at gmail.com> wrote:

> Hello,
>
> I'm attempting to install Nagios 3 on CentOS 5.1 i386.
>
> I've installed gd, gd-devel, freetype, libjpeg, libjpeg-devel, zlib,
> zlib-devel packages.
>
> I'm comping nagios 3 with the following options,
>
> ./configure --prefix=/opt/nagios --sysconfdir=/etc/nagios
> --localstatedir=/var/
> nagios --with-command-group=nagcmd --with-nagios-user=nagios
> --with-nagios-grou
> p=nagios --enable-event-broker --with-gd-lib=/usr/lib
> --with-gd-inc=/usr/includ
> e --with-mail=/usr/sbin/sendmail --enable-statusmap=yes
> --enable-statuswrl=yes
>
> Compile is successful. However there is no statusmap.cgi in sbin/ and I
> get apache error (file not found) on clicking  "Status Map".
>
> config.log  has,
>
> <snip>
> ........
> .....
> configure:5760: result: no
> configure:5768: checking for gdImagePng in -lgd (order 1)
> configure:5796: gcc -o conftest -g -O2 -I/usr/include   -L/usr/lib
> conftest.c -lgd -lttf -lpng -ljpeg -lz -lm  >&5
> /usr/bin/ld: cannot find -lttf
> collect2: ld returned 1 exit status
> configure:5802: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> ....
> ...
> </snip>
>
>
> <snip>
> ....
>
> | #define USE_XDDDEFAULT 1
> | /* end confdefs.h.  */
> |       /* Override any gcc2 internal prototype to avoid an error.  */
> | /* We use char because int might match the return type of a gcc2
> |     builtin and then its argument prototype would still apply.  */
> | char gdImagePng();
> |
> | int
> | main ()
> | {
> | gdImagePng()
> |   ;
> |   return 0;
> | }
> configure:5837: result: no
> configure:5844: checking for gdImagePng in -lgd (order 2)
> configure:5872: gcc -o conftest -g -O2 -I/usr/include   -L/usr/lib
> conftest.c -lgd  -lpng -ljpeg -lz -lm  >&5
> configure:5878: $? = 0
> configure:5882: test -z
>                          || test ! -s conftest.err
> configure:5885: $? = 0
> configure:5888: test -s conftest
> configure:5891: $? = 0
> configure:5906: result: yes
> configure:6206: checking ltdl.h usability
> configure:6218: gcc -c -g -O2 -I/usr/include  conftest.c >&5
> conftest.c:114:18: error: ltdl.h: No such file or directory
> configure:6224: $? = 1
> configure: failed program was:
> | /* confdefs.h.  */
> ....
> ....
> </snip>
>
> I'm not sure what the problem is.  Any ideas?
>
> Thanks in advance,
> Joey
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080314/a642aeef/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- 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