On Mon, May 12, 2008 at 7:12 AM, JK <jknapka@kneuro.net> wrote:
> Dave Phillips wrote:
> > Confusion rules here. My build of Csound 5.08 generated a file named
> _csnd.so, it is not linked to anything. The file libcsnd.so.5.1 is found in
> > OPCODEDIR64, and it too is not linked to any other object (other than
> itself).
> >
>
>  I think there is a disconnect in terminology.
>
>  You seem to be talking about symbolic links (in the filesystem). victor
>  is talking about linkage in the ABI sense: when a binary (executable)
>  file contains references to symbols defined in another such file,
>  those files must be "linked" (by a dynamic linker) in order to
>  resolve those references before execution can occur.  These two

I intuited something like that, thanks for the summary.

>  concepts are unrelated.  The important thing in this case is that
>  _csnd.so contains references to libcsnd.so.5.1, and therefore
>  the dynamic linker must be able to load lbcsnd.so.5.1 and resolve
>  the needed symbols whenever _csnd.so is loaded by the Python
>  interpreter.  For some reason the attempt to resolve these symbols
>  is failing; either because the dynamic linker cannot load
>  libcsnd.so.5.1, or because that library does not contain the symbols
>  of interest (or possibly other reasons I am forgetting).

In my case, if I understood correctly, for some reason the linking
file _csnd.so didn't contain the reference.  It still contained a
couple dozen references to other files like fltk, libogg, libsndfile,
etc.  The linked file libcsnd.so.5.1 was in the right place and
contained the symbols, but wasn't being sought.  I've no idea why.

-Chuckk

-- 
http://www.badmuthahubbard.com