The Python error might be fixed by creating a libpython2.4.so.1.0 symbolic
link in /usr/lib to whatever Python library you actually have, assuming that
2.4.2 is backward compatible with 2.4.1.
The stdc++ problem suggests a different GCC version; the rpm was built with
4.0.2. What distribution do you have ? Perhaps an rpm could be created for
that too.

On Tuesday 21 February 2006 22:01, Tobiah wrote:

>  [toby@sinewave toby]$ ldd /usr/local/lib/csound/plugins/libpy.so
>         linux-gate.so.1 =>  (0xffffe000)
>         libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0xb7f8d000)
>         libpython2.4.so.1.0 => not found
>         libutil.so.1 => /lib/libutil.so.1 (0xb7f89000)
>         libdl.so.2 => /lib/libdl.so.2 (0xb7f85000)
>         libm.so.6 => /lib/tls/libm.so.6 (0xb7f62000)
>         libc.so.6 => /lib/tls/libc.so.6 (0xb7e47000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> [toby@sinewave toby]$ ldd /usr/local/lib/csound/plugins/libloris.so
> /usr/local/lib/csound/plugins/libloris.so: /usr/lib/libstdc++.so.6: version `CXXABI_1.3.1' not found (required by /usr/local/lib/csound/plugins/libloris.so)
>         linux-gate.so.1 =>  (0xffffe000)
>         libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7ee5000)
>         libsndfile.so.1 => /usr/lib/libsndfile.so.1 (0xb7e92000)
>         libm.so.6 => /lib/tls/libm.so.6 (0xb7e6f000)
>         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7e67000)
>         libc.so.6 => /lib/tls/libc.so.6 (0xb7d4c000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
> 
> Now I remember that I had to force the rpm with --nodeps because of the libstdc++
> thing.  I couldn't figure out how to upgrade to the newer version.  As for
> the python, I'm running version 2.4.2.  I'm not sure why I don't have
> that libpython.
> 
> [toby@sinewave config]$ locate libpython2.4.so
> [toby@sinewave config]$