Problems Compiling the MySQL and PostgresSQL p lug-in's

[Kaplan, Andrew H.]

Karl,

I removed the config.cache file and recompiled the check_mysql plug-in. After I
installed
it on the remote machine, I ran the file from the shell prompt. I encountered
the following
error message:

./CHECK_MYSQL: /LIB/I686/LIBC.SO.6: VERSION 'GLIBC_2.3' NOT FOUND (REQUIRED BY
./CHECK_MYSQL)

I went to the directory in question and the libc.so.6 file is there as a
symbolic link pointing
to libc-2.2.5.so. I'm guessing I'll need a newer veresion of the gcc libraries
in order to cor-
rect this problem. The only thing is, will upgrading to the newer libraries, if
that is the way
to go, conflict with the MySQL database on the system? Your thoughts?

-----Original Message-----
From: Karl DeBisschop [mailto:karl at debisschop.net]
Sent: Monday, February 24, 2003 10:17 PM
To: Kaplan, Andrew H.
Cc: 'nagios-users at lists.sourceforge.net'
Subject: Re: [Nagios-users] Problems Compiling the MySQL and PostgresSQL
plug-in's


On Mon, 2003-02-24 at 12:50, Kaplan, Andrew H. wrote:
> I am having problems compiling the two SQL database plug-in's. I have
installed
> the MySQL 3.23.-55.1 server, client, and development libraries onto the
system.
> After that was done I reran the configure script for the Nagios plug-ins. I
> checked the plug-ins directory but the MySQL plug-in had not been created. The
> operating
> system that I am running everything on is Red Hat 8.0. Any ideas? Thanks.

Were the development libraries installed the first time you ran
configure? You may need to remove cached results (make distclean)

--
Karl



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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