[Xymon] update3: configure fails at RRD link, can't find libz.so

[Root, Paul]

Probably add -L /usr/local/lib/hpux32 to the build line.

Paul Root
Lead Internet Systems Eng
CenturyLink



> -----Original Message-----
> From: xymon-bounces at xymon.com
> [mailto:xymon-bounces at xymon.com] On Behalf Of Lynn Osburn
> Sent: Friday, April 08, 2011 12:21 PM
> To: Tim McCloskey; Williams, Doug (Consultant-RIC); xymon at xymon.com
> Subject: Re: [Xymon] update3: configure fails at RRD link,
> can't find libz.so
>
> Thanks for weighing in, Tim.
>
> by putting an echo statement in the build/Makefile.test-rrd
> we can see what is actually being done during the test that
> fails during the configure.server step
>
> On my system, that test-link function
>   @$(CC) $(CFLAGS) $(RRDDEF) $(RRDLIB) -o test-rrd test-rrd.o
> -lrrd $(PNGLIB)
>
> expands to look like this:
>   gcc -g -O -D_REENTRANT -DHPUX -L/usr/local/rrdtool/lib -o
> test-rrd test-rrd.o -lrrd
>
> If I run that compile manually, this is what I get:
>
> # gcc -g -O -D_REENTRANT -DHPUX -L/usr/local/rrdtool/lib -o
> test-rrd test-rrd.o -lrrd
> ld: Can't find dependent library "libz.so"
>
> I have installed 2 versions of zlib for HPUX.  The first was
> the version called out in the RRD documentation (zlib-1.2.3)
> and when that didn't work, I removed it and installed a more
> current version (zlib-1.2.5).  Changing versions didn't
> change the error, however.
>
>
> -Lynn
>
>
> -----Original Message-----
> From: Tim McCloskey [mailto:tm at freedom.com]
>
> I'm not familiar with HPUX, but do you have something like
> truss or strace available so you can see what's going on in
> startup?  If /usr/local/lib/hpux32/libz.so is good then maybe
> there is some silent version error that can be seen (ie
> rrdtool expects v1234 and yours is v3421).  Really just
> shot's in the dark....
> _______________________________________________
> Xymon mailing list
> Xymon at xymon.com
> http://lists.xymon.com/mailman/listinfo/xymon
>

This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.