statusmap.cgi compilation on HPUX 11i

[Andreas Ericsson]

cits.bogajewski at daimlerchrysler.com wrote:
> Hi Folks,
> 
> on my HPUX 11i

On systems other than *BSD and GNU/Linux, libraries usually get 
installed in weird paths.

>  the compilation of statusmap.cgi fails while the following 
> error occurs:
> 
> *** GD, PNG, and/or JPEG libraries could not be located... *********
> 
> My /etc/local/lib directory looks like this:
> 

This is definitely a weird path, even for HPUX. /etc is considered the 
system wide configuration directory on all unices.

> -rw-r--r--   1 root       sys         219288 Sep 20 14:50 libjpeg.a
> -rw-r--r--   1 root       sys            473 Sep 20 14:50 libjpeg.la
> -r-xr-xr-x   1 root       sys         192512 Sep 20 14:50 libjpeg.sl
> -rw-r--r--   1 root       sys         225768 Jan 14 13:06 libpng.a
> -rwxr-xr-x   1 root       sys            677 Jan 14 13:06 libpng.la
> -r-xr-xr-x   1 root       sys         200704 Jan 14 13:06 libpng.sl
> -rw-r--r--   1 root       sys         225768 Jan 14 13:06 libpng12.a
> -rwxr-xr-x   1 root       sys            687 Jan 14 13:06 libpng12.la
> -r-xr-xr-x   1 root       sys         200704 Jan 14 13:06 libpng12.sl
> -rw-r--r--   1 root       sys         323684 Jan 13 16:28 libgd.a
> -rw-r--r--   1 root       sys            880 Jan 13 16:28 libgd.la
> -r-xr-xr-x   1 root       sys         299008 Jan 13 16:28 libgd.sl
> ...
> 
> Also present are the header files within the include directory. So any 
> files necessary for compilation should be present in my opinion.
> 
> My configure command looks like this.
> ./configure --prefix=/opt/nagios --with-cgiurl=/nagios/cgi-bin 
> --with-htmurl=/nagios --with-nagios-user=nagios --with-nagios-grp=nagios 
> --with-gd-lib=/usr/local/lib --with-gd-inc=/usr/local/include
> 

I hope you're aware that you said /etc/local/lib above, and tried to 
compile with /usr/local/lib right here.

> Although the library path is explicitely providen, the compilation fails.
> 
> There is a following statement can be found within the error message:
> 
> NOTE: After you install the necessary libraries on your system:
>       1. Make sure /etc/ld.so.conf has an entry for the directory in
>          which the GD, PNG, and JPEG libraries are installed.
>       2. Run 'ldconfig' to update the run-time linker options.
>       3. Run 'make clean' in the Nagios distribution to clean out
>          any old references to your previous compile.
>       4. Rerun the configure script.
> 
> Unfortunately there is no ldconfig present on my system. In my opinion it 
> should work anyway. However, i am quite new to HPUX so i can be wrong.
> 

You most likely are. The LD_LIBRARY_PATH (or something, it's been 
deprecated on modern systems for a loong time) holds the equivalence of 
/etc/ld.so.conf.

> Got someone nagios on HPUX running?
> 

I think not. I know some people have it running on solaris, but with a 
shitload of GNU toys installed. I also believe those people were a bit 
more competent on the system in question. No offense meant.

> Would anyone maybe can help me? Many thanks in advance!
> 

Get some linux or *bsd dist installed and start poking around with it. 
HPUX isn't exactly the most common and developerfriendly platform 
around, so you'll most likely keep running into issues like this with a 
lot of opensource things.

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


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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