[Pdns-users] Building pdns RPMs using custom LDAP libraries/headers

[Nikolaos Milas]

On 19/3/2013 8:13 μμ, Nikolaos Milas wrote:

> But, as I mentioned, it even fails without any change in the spec
> file, simply trying to build with the standard CentOS 6 OpenLDAP
> packages. In that case, it should be using the default system lib dir:

In the meantime, I tried building PowerDNS 3.2 on CentOS 5.9 x86_64 
using 
http://www.monshouwer.eu/download/3rd_party/pdns-server/el5/SRPMS/pdns-server-3.2-1.el5.MIND.src.rpm 
and this worked fine with the standard CentOS OpenLDAP libs.

However, building using:

    LIBS="-L/usr/local/openldap/lib64"

    %build
    %configure \
         --sysconfdir=%{_sysconfdir}/powerdns \
         --libdir=%{_libdir} \
         --with-sqlite3 \
         --with-socketdir=/var/run/pdns-server \
         --with-modules="" \
         --with-dynmodules="pipe gmysql gpgsql gsqlite3 ldap"
    %{__make}

I am not sure it produces the required result:
...
/bin/sh ../../libtool --tag=CXX   --mode=link g++  -D_GNU_SOURCE -O2 -g 
-pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector 
--param=ssp-buffer-size=4 -m64 -mtune=generic -module -avoid-version 
-lrt -o libldapbackend.la -rpath /usr/lib64 ldapbackend.lo powerldap.lo 
-lldap_r -lz
...

I understand that the compiler probably still uses: /usr/lib64/ for ldap 
libs, although we instructed (?) it to use ldap libs from 
/usr/local/openldap/lib64.

So, there remain two questions:

1. How to build properly with custom LDAP libs?
2. Why we can't build correctly under CentOS 6, but only under CentOS 5?

Regards,
Nick