Re: build and run issues cvs version

[<de...@il...>]

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"