Re: compile python-ldap on macosx

[Jens V. <je...@zo...>]

as far as compiling python-ldap goes, here is the outcome of a couple=20
experiments i did yesterday. all were done with the current CVS HEAD:

- against self-compiled OpenLDAP 2.1.4 and self-compiled python 2.1.3:=20=

no problem.

- against built-in OpenLDAP and self-compiled python 2.1.3: no problem.=20=

i specified "/usr/lib" as library_dirs and "/usr/include" as=20
include_dirs. libs was "ldap_r lber ssl crypto" (sasl did not compile -=20=

could not find sasl.h, even though OS X has the library itself).

- against built-in OpenLDAP and the built-in python 2.2: fails with the=20=

error message that started this whole thread. the _ldap.so shared=20
module is not created because linking fails.

it seems that the culprit might be the built-in python2.2. the python=20
build flags, i assume, govern the build flags used when compiling these=20=

extension modules.

jens


On Sunday, Oct 27, 2002, at 08:12 US/Eastern, Michael Str=F6der wrote:

> Michael Engelhart wrote:
>> On Sunday, October 27, 2002, at 07:32  AM, Michael Str=F6der wrote:
>>> Sourceforge recently added Mac OS X to their compile farm:
>>> http://sourceforge.net/forum/forum.php?forum_id=3D113664
>>> Anyone interested in using that for testing python-ldap? We maybe=20
>>> could request the OpenDirectory standard package to be added to the=20=

>>> compile farm system.
> >
> > OpenLDAP is part of the default OS X install.  I guess the =
developers
> > would need access to the slapd.conf file to set the direcotry =
manager
> > name/password.
>
> Maybe my comment was misleading. I was only thinking about using Mac=20=

> OS X's LDAP client libs to compile binaries of python-ldap for Mac OS=20=

> X.
>
> Ciao, Michael.
>