Csound Csound-dev Csound-tekno Search About

[Csnd] Subject: _csnd.so unknown file type

Date2008-07-16 03:18
From" Partev Barr Sarkissian"
Subject[Csnd] Subject: _csnd.so unknown file type
Shouldn't it be a **.sco, rather than a **.so? Is there something about Python that allows the **.so?
Afraid I'm not a very Python savvy person.

- Partev



------------------------------------------------------------------------------------------------------------------------------



--- dominic.thibault@gmail.com wrote:

From: Dominic Thibault 
To: csound@lists.bath.ac.uk
Subject: [Csnd] _csnd.so unknown file type
Date: Tue, 15 Jul 2008 14:57:50 -0400

Hi folks,

I just finished building Csound5.08 from the source.  Everything  
seemed to
work flawlessly (no error while compiling) but when I tried loading the
Python API I realized it didn't work. If I load python and do 'import  
csnd',
I get the following :

Traceback (most recent call last):
   File "", line 1, in 
   File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ 
python2.5/csnd.py", line 7, in 
     import _csnd
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.5/ 
lib/python2.5/_csnd.so, 2): no suitable image found.  Did find:
         /Library/Frameworks/Python.framework/Versions/2.5/lib/ 
python2.5/_csnd.so: unknown file type, first eight bytes: 0x21 0x3C  
0x61 0x72 0x63 0x
68 0x3E 0x0A


My guess is that lib_csnd.a is not correctly compiled but I don't know  
what
I do wrong. I compiled using the same sources on a different computer  
(a Mac
Pro) and it worked there.

Any thoughts?

Here's my setup:
Macbook Pro
OSX 10.5.4
Python 2.5.2
Csound 5.08 (July 15 2008)


Thank you very much!



Dominic Thibault






Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"




_____________________________________________________________
Netscape.  Just the Net You Need.

Date2008-07-16 15:37
FromJK
Subject[Csnd] Re: Subject: _csnd.so unknown file type
  Partev Barr Sarkissian wrote:
> Shouldn't it be a **.sco, rather than a **.so? Is there something about Python that allows the **.so?
> Afraid I'm not a very Python savvy person.

*.so is a Unix shared library -- basically the equivalent of a Windows 
DLL. Python loads DLLs or .so libraries in order to gain access to 
foreign functionality (not implemented in Python).  Thus .so is probably 
the right extension here, and the original poster is seeing some actual 
problem.

-- JK

-- 
I do not particularly want to go where the money is -
  it usually does not smell nice there. -- A. Stepanov