On Thu, 24 Oct 2002, Ian Clarke wrote:
> ian at technic fish-is-still-an-idiot]$ ./streamServer.py
> Traceback (most recent call last):
> File "./streamServer.py", line 3, in ?
> from retrieveStream import *
> File "./retrieveStream.py", line 4, in ?
> from fecUtils import *
> File "./fecUtils.py", line 1, in ?
> import fec2,thread
> ImportError: libpython2.2.so.0.0: cannot open shared object file: No
> such file or directory
>
> :-(
the binary version of the module that you are trying to use was compiled
on debian. I'm guessing that your distro calls the file libpython rather
than libpython2.2. look at the makefile in the modules/ directory.
it is days like that I really hate linux. truely and deeply.
seriously. The reason is, in debian, libpython is python 2.1. The
streamer doesn't work with python 2.1. The only way to get pyhton 2.2 on
debian is to access it directly. Hence also the #! string at the top of
each file being python2.2 rather than python, which I suspect was your
issuewhen you mentioned about the files lacking the magic at the top.
Other than (a) changing debian (b) changing everything else (c) spending
half of my life learning autoconf, I don't have an easy solution other
than compile the module yourself *sigh*. I know it';s a stupid and lame
answer, and I'm sure you're all having a good laugh at the lazy stupid
fish right now.
somoene once suggested bundling wtih a binary python. sometimes, i think
there is some merit in this (the windows version actulyl does ship
withpython22.dll, btu anyhow)
- fish
_______________________________________________
devl mailing list
devl at freenetproject.org
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
