Menu
▾
▴
python-ldap-dev
|
From: <de...@il...> - 2002-02-28 07:30:23
|
Hi,
two issues with code from cvs as of 2/28/02. First, python setup.py build
complained about:
warning: build_py: file Lib/ldap.py (for module ldap) not found
There was no ldap.py file anywhere in the module I got from cvs.
I put a ldap.py file from python-ldap-1.10alpha3 into Lib and was able to
build and install.
However, when I try to import ldap or _ldap I get denied:
$ python
Python 2.0.1 (#1, Jun 24 2001, 18:39:34)
[GCC 2.95.3 20010315 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import ldap
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.0/site-packages/ldap/__init__.py", line 5, in ?
from _ldap import *
ImportError: cannot open shared object file: cannot load shared object
file: No such file or directory
>>> import _ldap
Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: cannot open shared object file: cannot load shared object
file: No such file or directory
>>>
--
---
Dennis Sacks
de...@il...
"Things are falling down on me, heavy things I could not see"
|
|
From: Jens V. <je...@zo...> - 2002-02-28 13:41:20
|
will setup.py fail when you run it and there is no ldap.py? i dimly remember seeing that warning but the build process never failed, i think that message is benign and doesn't mean much. just sticking in a piece of code from a *totally* different version of python-ldap is probably not a good solution and will lead to problems. jens On Thursday, February 28, 2002, at 02:27 , de...@il... wrote: > Hi, > > two issues with code from cvs as of 2/28/02. First, python setup.py build > complained about: > > warning: build_py: file Lib/ldap.py (for module ldap) not found > > There was no ldap.py file anywhere in the module I got from cvs. > > I put a ldap.py file from python-ldap-1.10alpha3 into Lib and was able to > build and install. > > However, when I try to import ldap or _ldap I get denied: > > $ python > Python 2.0.1 (#1, Jun 24 2001, 18:39:34) > [GCC 2.95.3 20010315 (release)] on linux2 > Type "copyright", "credits" or "license" for more information. >>>> import ldap > Traceback (most recent call last): > File "<stdin>", line 1, in ? > File "/usr/lib/python2.0/site-packages/ldap/__init__.py", line 5, in ? > from _ldap import * > ImportError: cannot open shared object file: cannot load shared object > file: No such file or directory >>>> import _ldap > Traceback (most recent call last): > File "<stdin>", line 1, in ? > ImportError: cannot open shared object file: cannot load shared object > file: No such file or directory >>>> > > > -- > --- > Dennis Sacks > de...@il... > "Things are falling down on me, heavy things I could not see" > > > > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
|
From: <de...@il...> - 2002-02-28 16:48:17
|
On Thu, 28 Feb 2002, Jens Vagelpohl wrote:
> will setup.py fail when you run it and there is no ldap.py? i dimly
> remember seeing that warning but the build process never failed, i think
> that message is benign and doesn't mean much.
> just sticking in a piece of code from a *totally* different version of
> python-ldap is probably not a good solution and will lead to problems.
You have a very good point that I cannot dispute. It was late and I don't
remember now why I thought that would help.
I started over with a clean copy of the python-ldap from cvs, edited
setup.cfg, ran python setup.py build & python setup.py install.
When I try to import ldap this is what I see:
$ python
Python 2.0.1 (#1, Jun 24 2001, 18:39:34)
[GCC 2.95.3 20010315 (release)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import ldap
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "/usr/lib/python2.0/site-packages/ldap/__init__.py", line 5, in ?
from _ldap import *
ImportError: cannot open shared object file: cannot load shared object
file: No such file or directory
>>>
--
---
Dennis Sacks
de...@il...
"Things are falling down on me, heavy things I could not see"
|
|
From: Jens V. <je...@zo...> - 2002-02-28 17:30:59
|
you could check which libraries the resulting .so file is linked against and verify if those libraries are in the place they should be. the command to check the linked libraries escapes me right now, i hardly ever use it : / jens On Thursday, February 28, 2002, at 11:44 , de...@il... wrote: > On Thu, 28 Feb 2002, Jens Vagelpohl wrote: > >> will setup.py fail when you run it and there is no ldap.py? i dimly >> remember seeing that warning but the build process never failed, i think >> that message is benign and doesn't mean much. > >> just sticking in a piece of code from a *totally* different version of >> python-ldap is probably not a good solution and will lead to problems. > > You have a very good point that I cannot dispute. It was late and I don't > remember now why I thought that would help. > > I started over with a clean copy of the python-ldap from cvs, edited > setup.cfg, ran python setup.py build & python setup.py install. > > When I try to import ldap this is what I see: > > $ python > Python 2.0.1 (#1, Jun 24 2001, 18:39:34) > [GCC 2.95.3 20010315 (release)] on linux2 > Type "copyright", "credits" or "license" for more information. >>>> import ldap > Traceback (most recent call last): > File "<stdin>", line 1, in ? > File "/usr/lib/python2.0/site-packages/ldap/__init__.py", line 5, in ? > from _ldap import * > ImportError: cannot open shared object file: cannot load shared object > file: No such file or directory >>>> > > > -- > --- > Dennis Sacks > de...@il... > "Things are falling down on me, heavy things I could not see" |
|
From: <mi...@st...> - 2002-02-28 21:47:21
|
Jens Vagelpohl wrote:
> you could check which libraries the resulting .so file is linked against
> and verify if those libraries are in the place they should be. the
> command to check the linked libraries escapes me right now, i hardly
> ever use it :
You probably mean ldd. See the output on my system below (output
varies depending on features compiled into OpenLDAP libs).
Ciao, Michael.
# ldd /usr/lib/python2.2/site-packages/_ldap.so
libldap.so.2 => /usr/local/openldap2/lib/libldap.so.2
(0x40022000)
liblber.so.2 => /usr/local/openldap2/lib/liblber.so.2
(0x40052000)
libc.so.6 => /lib/libc.so.6 (0x4005e000)
libsasl.so.7 => /usr/local/sasl/lib/libsasl.so.7 (0x40171000)
libkrb4.so.2 => /usr/local/krb5/lib/libkrb4.so.2 (0x4017e000)
libdes425.so.3 => /usr/local/krb5/lib/libdes425.so.3
(0x40193000)
libkrb5.so.3 => /usr/local/krb5/lib/libkrb5.so.3 (0x40197000)
libk5crypto.so.3 => /usr/local/krb5/lib/libk5crypto.so.3
(0x401f4000)
libcom_err.so.3 => /usr/local/krb5/lib/libcom_err.so.3
(0x40206000)
libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40208000)
libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6
(0x402c0000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
libdb-3.1.so => /usr/lib/libdb-3.1.so (0x40384000)
libdl.so.2 => /lib/libdl.so.2 (0x40401000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40404000)
libpam.so.0 => /lib/libpam.so.0 (0x40432000)
libresolv.so.2 => /lib/libresolv.so.2 (0x4043b000)
|
|
From: <mi...@st...> - 2002-02-28 21:47:37
|
de...@il... wrote: > > warning: build_py: file Lib/ldap.py (for module ldap) not found Simply ignore that. It solely has to do with a brain-dead limitation of DistUtils. > There was no ldap.py file anywhere in the module I got from cvs. Yes, that's right. > I put a ldap.py file from python-ldap-1.10alpha3 into Lib and was able to > build and install. Don't do that!!! > Traceback (most recent call last): > File "<stdin>", line 1, in ? > File "/usr/lib/python2.0/site-packages/ldap/__init__.py", line 5, in ? > from _ldap import * > ImportError: cannot open shared object file: cannot load shared object > file: No such file or directory Adjust /etc/ld.so.conf or set LD_LIBRARY_PATH to point to the directory containing the shared libs of OpenLDAP 2. Ciao, Michael. |
Thanks for helping keep SourceForge clean.
X