[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Compiling OpenLDAP on Mac OS X v10.3 Panther
- To: openldap-software@OpenLDAP.org
- Subject: Compiling OpenLDAP on Mac OS X v10.3 Panther
- From: Finlay Dobbie <finlay.dobbie@gmail.com>
- Date: Sun, 27 Mar 2005 20:58:17 +0100
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=VhliMD54qGyxZIRufHT0SeLIpxJwPEvwb4wFaksiry/sU51q4+veU5s9svWOkocuAvVKw7NRKpUHe9MXEkKpNaCuYhi0YnK3muBq08wb34lcJ/VehmzA3/PeSgfUhA0XVbWX9yrItgZQ6JR8lVkurPBlvr+E+IMKg+46isy6BJM=
Attempting to compile OpenLDAP (2.3.2beta or 2.2.24) results in the
following message:
cc -g -O2 -o dntest dntest.o ./.libs/libldap.a
/Users/finlay/openldap-2.3.2beta/libraries/liblber/.libs/liblber.a
../../libraries/liblber/.libs/liblber.a
../../libraries/liblutil/liblutil.a -lssl -lcrypto
ld: Undefined symbols:
_res_9_dn_expand
_res_9_query
make[2]: *** [dntest] Error 1
make[1]: *** [all-common] Error 1
make: *** [all-common] Error 1
These symbols are in libresolv. There are two solutions: either use
the BIND 8 resolver API or add -lresolve to the LDFLAGS. However, this
should be detected by the build system so it compiles out of the box.
Jason Townsend provided a patch, but it was rejected unequivocally
(see <http://www.openldap.org/its/index.cgi/Build?id=2763;expression=lresolv;statetype=-1>).
Is building out of the box not a goal?
Also, there is no method in the config script of specifying where
Berkely DB is installed. Given that it defaults to installing in
/usr/local/BerkeleyDB.4.x, would it not make sense to support
specifying a path to the BDB installation?
-- Finlay