On Tue, 2010-06-22 at 02:54 -0700, Tom wrote: > > 6) > > $ ocropus-pages -h > > Traceback (most recent call last): > > File "/usr/bin/ocropus-pages", line 13, in <module> > > import ocropy > > File "/usr/lib/python2.5/site-packages/ocropy/__init__.py", line > 4, in > > <module> > > from ocropus import * > > File "/usr/lib/python2.5/site-packages/ocropus.py", line 10, in > > <module> > > import _ocropus > > ImportError: libocropus.so: cannot open shared object file: No such > file > > or directory > > Check whether there is a "/usr/local/lib/libocropus.so". Yes. > If not, your > build failed somehow; you need to figure out why it didn't get > installed. If there is, you need to add /usr/local/lib to your > LD_LIBRARY_PATH so that Python can find it. That solved the problem. ocropus-pages itself uses with, so python 2.5 barfed. > > > but ocropus page foo.png ran. The former is in /usr/bin, the latter > > in /usr/local/bin. > > /usr/bin/ocropus sounds like it was installed from a package rather > than from the sources. The ocropus command itself is pure C++ and > doesn't use Python. It's /usr/bin/ocropus-pages and /usr/local/bin/ocropus for me. Wouldn't it be more consistent to use only /usr or only /usr/local?
> > Try "dpkg -S /usr/bin/ocropus". If that yields a result, you are > running the packaged version. I double-checked (with correct paths): no package. Ross -- You received this message because you are subscribed to the Google Groups "ocropus" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/ocropus?hl=en.
