Hi all. The _csnd module has broken in 5.07 on linux, caused by the patch I 
provided to give a versioned SONAME to libcsnd. For some strange reason, 
although the soname is set only[1] for the build with the SHLINKFLAGS 
optional argument to SharedLibrary, it gets passed on to _csnd, which is 
causing failures at runtime:

>>> import csnd
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "/usr/lib/python2.4/site-packages/csnd.py", line 7, in ?
    import _csnd
ImportError: /usr/lib/python2.4/site-packages/_csnd.so: undefined symbol: 
_ZN23CsoundPerformanceThreadD1Ev

This is because while _csnd needs libcsnd.so.5.1, it has that SONAME itself, 
so it doesn't load the real library.
Removing the soname from libcsnd.so (and thus, from _csnd) fixes the issue. Is 
this a bug in scons, or in the SConstruct? My gut tells me it's scons, but 
I'm not sure. I tried several scons versions to no avail. Manually clearing 
the flag before building _csnd also fixes the issue: adding the following 
just after creating the csndPythonEnvironment:

      if '-Wl,-soname=libcsnd.so.5.1' in csndPythonEnvironment['SHLINKFLAGS']:
             
csndPythonEnvironment['SHLINKFLAGS'].remove('-Wl,-soname=libcsnd.so.5.1')



 Although I imagine that there is a cleaner solution to the problem (without 
invlolving knowing in advance the soname of libcsnd).

Any ideas?

[1] I think. I'm not an expert with scons, but it sounds reasonable for a flag 
to be only for that specific build when specifying it there.
-- 

	Felipe Sateler