On Wed, 2009-02-11 at 19:40 +0100, Peter Eckel wrote:
Hi,
when building syslog-ng from the latest git source, I found a problem with libdbi that occurs on my Redhat ES 5.2 systems that do not have libdbi installed (neither have my customer's systems):
commit 6ca874d7ea362e4f0286245542f7ea601743c72d Author: Balazs Scheidler <bazsi@balabit.hu> Date: Mon Feb 9 11:44:09 2009 +0100
[configure] added kludge to recognize libdbi without an installed dbi.pc file
libdbi does not always install a pkg-config file, work without one, assuming it was installed to the default location.
Unfortunately configure now also recognizes libdbi if it is not installed at all:
[sec@linux1 sbin]$ rpmquery libdbi package libdbi is not installed
[sec@linux1 sbin]$ rpmquery libdbi-devel package libdbi-devel is not installed
[sec@linux1 syslog-ng.git]$ ./configure --disable-ssl --disable-sql --disable-ipv6 --enable-pcre --prefix=/opt/sec/local CFLAGS=-I/opt/sec/local/include LDFLAGS=-L/opt/sec/local/lib [...] checking for dlsym in -ldl... (cached) yes checking for LIBDBI... no checking for LIBDBI... yes
Ahh.. you're right. This patch should fix it: commit 6b299cf2c9e577acd6b48eb686cec45ff209aa6a Author: Balazs Scheidler <bazsi@balabit.hu> Date: Sat Feb 14 19:10:54 2009 +0100 [configure] fixed LIBDBI detection, the previous change always enabled SQL support regardless if libdbi was installed or not -- Bazsi