Menu
▾
▴
|
From: Kyle M. <ky...@kl...> - 2004-10-27 19:35:03
|
Hi, I'm trying to compile and install python-ldap-2.0.3 and 2.0.4 on Mac OS X 10.3, but I seem to be getting some errors, and nothing ends up getting installed. The weirdest part about this is that I originally had this working just fine not even a week ago with version 2.0.3. If I uncompress the older (2.0.3) version and try to install, I still get the following: root@localhost:~ # python setup.py install extra_compile_args: extra_objects: include_dirs: /usr/local/openldap-REL_ENG_2_1/include /usr/include/sasl /usr/local/sasl/include/sasl library_dirs: /usr/local/openldap-REL_ENG_2_1/lib /usr/lib/sasl /usr/local/sasl/lib libs: ldap_r lber sasl2 ssl crypto running install running build running build_py file Lib/ldap.py (for module ldap) not found file Lib/ldap/schema.py (for module ldap.schema) not found file Lib/ldap.py (for module ldap) not found file Lib/ldap/schema.py (for module ldap.schema) not found running build_ext building '_ldap' extension gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-protoo gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -Wall -Wstrict-protoo Modules/LDAPObject.c:20:18: sasl.h: No such file or directory Modules/LDAPObject.c:492: error: parse error before "sasl_interact_t" Modules/LDAPObject.c:494: warning: function declaration isn't a prototype Modules/LDAPObject.c: In function `interaction': Modules/LDAPObject.c:495: error: `interact' undeclared (first use in this function) Modules/LDAPObject.c:495: error: (Each undeclared identifier is reported only once Modules/LDAPObject.c:495: error: for each function it appears in.) Modules/LDAPObject.c:498: error: `SASLObject' undeclared (first use in this function) Modules/LDAPObject.c:495: warning: unused variable `dflt' Modules/LDAPObject.c: In function `py_ldap_sasl_interaction': Modules/LDAPObject.c:546: error: `sasl_interact_t' undeclared (first use in this function) Modules/LDAPObject.c:546: error: `interact' undeclared (first use in this function) Modules/LDAPObject.c:549: error: `SASL_CB_LIST_END' undeclared (first use in this function) Modules/LDAPObject.c: In function `l_ldap_sasl_interactive_bind_s': Modules/LDAPObject.c:562: warning: unused variable `cred' Modules/LDAPObject.c:569: warning: unused variable `version' Modules/LDAPObject.c:571: warning: unused variable `defaults' error: command 'gcc' failed with exit status 1 -Kyle Mott |
|
From: <mi...@st...> - 2004-11-03 21:10:18
|
Kyle Mott wrote: > > include_dirs: /usr/local/openldap-REL_ENG_2_1/include /usr/include/sasl > /usr/local/sasl/include/sasl > [..] > Modules/LDAPObject.c:20:18: sasl.h: No such file or directory First I don't know Mac OS X. But where's your sasl.h located? You have to set the appropriate include directories in setup.cfg. Or turn off SASL in setup.cfg if you don't need it at all. Ciao, Michael. |
|
From: Jens V. <je...@da...> - 2004-11-03 21:31:00
|
On Nov 3, 2004, at 17:58, Michael Str=F6der wrote: > Kyle Mott wrote: > > > > include_dirs: /usr/local/openldap-REL_ENG_2_1/include=20 > /usr/include/sasl > > /usr/local/sasl/include/sasl > > [..] > > Modules/LDAPObject.c:20:18: sasl.h: No such file or directory > > First I don't know Mac OS X. > > But where's your sasl.h located? You have to set the appropriate=20 > include directories in setup.cfg. Or turn off SASL in setup.cfg if you=20= > don't need it at all. By default OS X does not have SASL header files. At least I cannot find=20= them on my 10.3.5, even though it has sasl-libraries in /usr/lib and=20 /usr/lib/sasl2 jens --------------- Jens Vagelpohl je...@ze... Software Engineer +49-(0)441-36 18 14 38 Zetwork GmbH http://www.zetwork.com/ |
|
From: <mi...@st...> - 2004-11-03 21:52:54
|
Jens Vagelpohl wrote: > > By default OS X does not have SASL header files. At least I cannot find > them on my 10.3.5, even though it has sasl-libraries in /usr/lib and > /usr/lib/sasl2 I'd add an example setup.cfg for Mac OS X to the source distribution under Build/ if you provide one. Ciao, Michael. |
|
From: Jens V. <je...@da...> - 2004-11-03 22:04:54
|
On Nov 3, 2004, at 22:50, Michael Str=F6der wrote: > Jens Vagelpohl wrote: > > > > By default OS X does not have SASL header files. At least I cannot=20= > find > > them on my 10.3.5, even though it has sasl-libraries in /usr/lib and > > /usr/lib/sasl2 > > I'd add an example setup.cfg for Mac OS X to the source distribution=20= > under Build/ if you provide one. Hallo Michael, All I do is remove "sasl2" from the "libs" directive in setup.cfg. Then=20= it compiles. Is that enough modification to qualify inclusion as a=20 separate sample setup.cfg? jens --------------- Jens Vagelpohl je...@ze... Software Engineer +49-(0)441-36 18 14 38 Zetwork GmbH http://www.zetwork.com/ |
|
From: <mi...@st...> - 2004-11-03 22:23:10
|
Jens Vagelpohl wrote: > > All I do is remove "sasl2" from the "libs" directive in setup.cfg. Then > it compiles. Is that enough modification to qualify inclusion as a > separate sample setup.cfg? Well, some people might wanna get spoon-fed. ;-) Any other platform-specific DistUtils options for e.g. binary packages under Mac OS X? Ciao, Michael. |
|
From: Jens V. <je...@da...> - 2004-11-03 22:54:45
|
On Nov 3, 2004, at 23:15, Michael Str=F6der wrote: > Jens Vagelpohl wrote: >> All I do is remove "sasl2" from the "libs" directive in setup.cfg.=20 >> Then it compiles. Is that enough modification to qualify inclusion as=20= >> a separate sample setup.cfg? > > Well, some people might wanna get spoon-fed. ;-) > > Any other platform-specific DistUtils options for e.g. > binary packages under Mac OS X? Doing python setup.py --help-commands doesn't reveal anything special=20 for OS X. I don't think there are any OS X-related special options. jens |
