On 22/3/2013 6:23 pm, a b wrote:
I did not mean that literally, sorry for the confusion. What I meant
is that you muss pass the equivalent of
--libdir=/usr/local/openldap/lib64 by using --libdir=%{_libdir}, which
is a special RPM built-in macro.
Thanks for your assistance.
Sorry, I am not a specialist in building apps, so instructions should be
clear otherwise I have to experiment. :-(
What this means is that your ~/.rpmmacros file is either incorrect or
non-existent.
Until now, I always use a simple:
$ cat .rpmmacros
%_topdir %(echo $HOME)/rpmbuild
which has worked fine in many builds I have, and it works fine when I
build pdns-server on CentOS 5.
However, I see your point: I should set (in .rpmmacros) something like:
%_libdir /usr/local/openldap/lib64
Yet, my earlier question remains: Can I set multiple paths, like:
%_libdir /usr/lib64,/usr/local/openldap/lib64
...? Is it supported?
On 22/3/2013 6:06 pm, a b wrote:
While technically not necessary, CFLAGS must often contain -L and -R
> switches to work around buggy or incorrectly coded ./configure files.
Ditto for LDFLAGS.
Do you set CFLAGS and LDFLAGS? What do they look like?
I don't see any CFLAGS or LDFLAGS specified in the spec file.
When I build (as an example) Dovecot, I use in the spec file (before
./configure):
export CPPFLAGS="${CPPFLAGS} -I/usr/local/openldap/include"
export LDFLAGS="${LDFLAGS} -L/usr/local/openldap/lib64 -lldap -llber"
Should I try the same here?
You should rebuild openldap RPM with the above .rpmmacros file
> sitting in your home directory.
I understand, however I don't want to mess around with this package,
although I see your point and I think it's valid. I'll pass your
suggestions to the LTB project maintainers as they are responsible for
these builds.
Thanks again and regards,
Nick
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
