[Sugar-devel] amRe: [Cs-dev] Sugar on a Stick - and OLPCsound/Csound

[Peter Robinson]

>> Hello, Peter et al. -
>>
>> Your latest Csound5.10 patch finally made it out to updates-testing today,
>> and I was able to install it on SoaS (Sugar 84) and test it out.
>>
>> Unfortunately it aborts with much the same (if not exactly) as before. Log:
>>
>> /usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning: the
>> sha module is deprecated; use the hashlib module instead
>>
>> import sha
>>
>> Traceback (most recent call last):
>>
>> File "/usr/bin/sugar-activity", line 21, in <module>
>>
>> main.main()
>>
>> File "/usr/lib/python2.6/site-packages/sugar/activity/main.py", line 105, in
>> main
>>
>> module = __import__(module_name)
>>
>> File "/home/liveuser/Activities/OurMusic.activity/ourmusic.py", line 42, in
>> <module>
>>
>> import csndsugui
>>
>> File "/home/liveuser/Activities/OurMusic.activity/csndsugui.py", line 36, in
>> <module>
>>
>> import csnd
>>
>> File "/usr/lib/python2.6/site-packages/csnd.py", line 7, in <module>
>>
>> import _csnd
>>
>> ImportError: /usr/lib/libcsnd.so.5.1: undefined symbol: csoundGetInputBuffer
>>
>>
>>
>> Observations: /usr/lib/ contains libcsound.so.5.1 and 5.2, but only
>> libcsnd.so.5.1. (I've no idea if this is significant or not.) I note that
>> Sugar 82 - designed for 5.08 - (at least on my OLPC) contains none of these
>> files.
>>
>> TamTamMini plays fine on both 82 and 84; of course it only plays samples.
>>
>> TamTamSynthLab seems to work fine with 82 (no errors), but not in 84 - where
>> the log shows a multitude of .so files incompatible with Csound5.10 (stated
>> as 2.0 and 1.6??). And, following that, an even larger list of illegal
>> opcodes and errors.
>>
>> If I were to guess something, it would be this: is perhaps libcsnd.so.5.2
>> required for Csound5.10?
>
> That sounds like a good idea to me.

That's what's compiled out of the csound 5.10.1 pacakge. Its not
something you can accidentally pick the wrong one because the Fedora
build system build everything in a fresh chroot env.

I wonder if the issue isn't due to a API change in the newer release?

Peter