Csound on Ubuntu

Felipe Sateler fsateler at debian.org
Sat Mar 5 15:52:15 UTC 2011


On Sat, Mar 5, 2011 at 07:24, Reinhard Tartler <siretart at tauware.de> wrote:
> On Sat, Mar 05, 2011 at 00:50:59 (CET), Felipe Sateler wrote:
>
>> On Sun, Feb 27, 2011 at 22:32, Felipe Sateler <fsateler at debian.org> wrote:
>>> On Sun, Feb 27, 2011 at 22:20, Ryan Kavanagh <ryanakca at kubuntu.org> wrote:
>>>> Hi Felipe,
>>>>
>>>> On Sun, Feb 27, 2011 at 09:49:23PM +0000, Felipe Sateler wrote:
>>>>> Could any of the Ubuntu-using team members please check out the
>>>>> python-csoundac package in Ubuntu. I've had a report that its broken,
>>>>> but I don't have a Ubuntu system to try it. Please try to import the
>>>>> python module (import CsoundAC) and report if it works.
>>>>
>>>> I get the following:
>>>>
>>>> ryan at lambda:~$ python -c "import CsoundAC"
>>>> Traceback (most recent call last):
>>>>  File "<string>", line 1, in <module>
>>>>  File "/usr/lib/python2.6/dist-packages/CsoundAC.py", line 25, in <module>
>>>>    _CsoundAC = swig_import_helper()
>>>>  File "/usr/lib/python2.6/dist-packages/CsoundAC.py", line 21, in swig_import_helper
>>>>    _mod = imp.load_module('_CsoundAC', fp, pathname, description)
>>>> ImportError: /usr/lib/python2.6/dist-packages/_CsoundAC.so: undefined symbol: _ZTIN6csound4NodeE
>>>
>>> OK, this seems like the same error. Now, could you please try the
>>> following? This will be a bit more annoying, unfortunately.
>>>
>>> Build the source package corresponding to tag debian/5.12.1.dfsg-5,
>>> installing it and trying again (this is to check if the problem was
>>> some buildd temporary issue). Then try the latest git HEAD.
>>>
>>> I think I fixed this bug in commit 018514f, but I'm not sure.
>>
>> OK, natty, which has 5.13 exhibits this problem too. Can the ubuntu
>> build logs be obtained from somewhere?
>
> sure. go to: https://launchpad.net/ubuntu/+source/csound
>
> select the version of the package you are interested in, expand text by
> clicking on the triangle left next to the package symbol, then click on
> the architecture name below the changelog and diff for the upload. This
> will give you the link to the buildjob, where you'll find the link to
> the buildlog.


OK, the problem seems to be -as-needed. Compiling with -no-as-needed
results in a correct binary (only in Ubuntu, Debian binaries are OK
even with -as-needed). Why does this fail in Ubuntu but not in Debian?
Any ideas?

-- 

Saludos,
Felipe Sateler



More information about the pkg-multimedia-maintainers mailing list