MonitorWare Knowledge Base

Hi, maybe someone can help.

When installing on REHL5 64bit i use this configure command

./configure --enable-mysql --enable-imfile

i get this error:

checking mysql/mysql.h usability... yes
checking mysql/mysql.h presence... yes
checking for mysql/mysql.h... yes
checking for mysql_config... yes
checking for mysql_init in -lmysqlclient... no
configure: error: in `/root/rsyslog/rsyslog-3.20.2':
configure: error: MySQL library is missing
See `config.log' for more details.

in config.log:

configure:26760: gcc -o conftest -g -O2 -W -Wall -Wformat-security -Wshadow -Wcast-align -Wpointer-arith -Wmissing-format-attribute -g conftest.c -lmysqlclient -L/usr/lib64/mysql -lmysqlclient -lz -lcrypt -lnsl -lm -L/usr/lib64 -lssl -lcrypto >&5
/usr/bin/ld: skipping incompatible /usr/lib/libz.so when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/libz.a when searching for -lz
/usr/bin/ld: cannot find -lz

OS Version is: Linux myhost.mydomain.tld 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

When removing mysql-directive the configure runs.

why the heck is rsyslog claiming libz incompatible, why searching in /usr/lib instead /usr/lib64? How to resolve?

thank you.

• Custom written rsyslog.conf?
• Maintenance Contract?
• Installation support?

due to my "demand" i just build a new CentOS5.2x64 machine just like i did the RHEL5.2 and tried to do the same think.

and it did not meet my expetationes (since its also RHEL Based, same Source):

IT WORKED

Strange? I would really like to understand what is going on here (and went wrong on the REHL5). Maybe someone shares my interest.

Ok, so far. next problem:

howto install the just compiled/prepared software on another machine? since when i move all this configure/make -ed directory back to REHL i cant make install.

think error? how to do then?

I am following with quite some interest, but I unfortunately do not have RHEL available for testing. I think the recent version has a (quite old) version of rsyslog. Maybe it helps to install that RPM and then copy over the files. But, granted, that's crude...

If there is a final solution, I'll see that I get it to the rsyslog wiki.

Rainer

rgerhards wrote: Maybe it helps to install that RPM and then copy over the files.

Thats exactly waht i dont wanna do, since the "original" distributed rsyslog is version 2.0.0, so are the rpm. Far too old for our demand.

so what i am now evaluating is buidl all this on a CentOS 5.2 and move it to RHEL5 then.

Where i am stuck is, how to get to RPM from the make -ed or make installed -ed on CentOS..... have never done such.

well.. the crude way is to look where rsyslogd and the plugins are located and copy them over... There is nothing but this. But of course, that's not a nice way to do it. But maybe a last resort if nobody else comes up with a solution...

rgerhards wrote: But of course, that's not a nice way to do it. But maybe a last resort if nobody else comes up with a solution...

Thats it.... not a nice way. thats the reason why i am trying to figure out how to create such a RPM containing the binarys, so i can distribute that compiled rsyslog to any RHEL machine for any sort of admin. We have quiet some Servers. CP is easy, and fortunatly make install tells me where the files are. So the remains is just some work to do and to learn how such a rpm is to be build.

If i manage to create a fairly public useable procedure, i will keep you updated.

Anyhow if someone comes up with an idea why i have the initial problem, iwould be willing to learn, because solving a problem is better than circumventing it.

Just a bit to improve the overall picture. rsyslog uses GNU autotools, which is what configure[1] builds. So in essence, the part that fails is outside of rsyslog, and this is the other reason why I am clueless. One thing you could try is double-check that you really have the mysql development files (mysql-devel package usually...) on the system. If you have (what I think), I do not have a real idea yet why it claims it isn't - maybe a path issue (and this is where we go into RHEL land ).

[1] EDIT: "configure" is actually build by autotools, so it itself is a generated file. It is build based on various files you do not see in the distribution tarball, but there is nothing unusual done in rsyslog. So, in theory, other packages that query mysql-devel should have issues similar to the one rsyslog experiences...

After digging deep into it, i finaly made it configure, make and make install on RHEL5.x 64bit.

beside the usual dependencies that are allready well documented there are two more:

openssl-devel.x86_64
zlib-devel.x86_64

these two are not (or at least seem not to be) automaticly installed in this distro. After installing those, all does workout fine.

rgerhards wrote:If there is a final solution, I'll see that I get it to the rsyslog wiki.

so we are at the state to have a final solution

Greetings,
Joe