I'll do another Linux build when I can, either tonight or early next week. Perhaps your LD_LIBRARY_PATH also needs to be updated. 

However, currently I only test on Fedora Core 1. This may change soon.

Regards,
Mike

-----Original Message-----
From: Dave Phillips 
Sent: Oct 13, 2005 11:47 AM
To: csound@lists.bath.ac.uk
Subject: [Csnd] CsoundVST problem

Greetings:

  I've successfully built and installed Cs5 from CVS sources on 
AGNULA/Demudi 1.2.1. GCC is 3.3.5, all other required packages are up to 
date and correctly installed.

  The csound binary works fine, realtime appears to be working perfectly 
in my very brief tests, but CsoundVST won't start. It complains :

    CsoundVST: error while loading shared libraries: _CsoundVST.so: 
cannot open shared object file: Error 40

  Any suggestions ? My PYTHONPATH includes /usr/local/lib, where the 
file resides.

Best,

dp


 
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk

Greetings:

  Copying _CsoundVST.so to /usr/lib solved the problem. I'll add 
/usr/local/lib to LD_LIBRARY_PATH too.

  Thanks for the help !

Best,

dp


Michael Gogins wrote:

>I'll do another Linux build when I can, either tonight or early next week. Perhaps your LD_LIBRARY_PATH also needs to be updated. 
>
>However, currently I only test on Fedora Core 1. This may change soon.
>
>Regards,
>Mike
>
>-----Original Message-----
>From: Dave Phillips 
>Sent: Oct 13, 2005 11:47 AM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd] CsoundVST problem
>
>Greetings:
>
>  I've successfully built and installed Cs5 from CVS sources on 
>AGNULA/Demudi 1.2.1. GCC is 3.3.5, all other required packages are up to 
>date and correctly installed.
>
>  The csound binary works fine, realtime appears to be working perfectly 
>in my very brief tests, but CsoundVST won't start. It complains :
>
>    CsoundVST: error while loading shared libraries: _CsoundVST.so: 
>cannot open shared object file: Error 40
>
>  Any suggestions ? My PYTHONPATH includes /usr/local/lib, where the 
>file resides.
>
>Best,
>
>dp
>
>
> 
>  
>

On Thu, 2005-10-13 at 13:13 -0400, Dave Phillips wrote:
> Greetings:
> 
>   Copying _CsoundVST.so to /usr/lib solved the problem. I'll add 
> /usr/local/lib to LD_LIBRARY_PATH too.
> 
>   Thanks for the help !
> 

Greetings from a "lurker"...

I'll bet you know this Dave, but you shouldn't have to
add /usr/local/lib to LD_LIBRARY_PATH - that's a bit of a hack. What is
supposed to happen is that /etc/ld.so.conf contains a list of paths and
then keeps a cache of library files. To update the cache, you should run
(as root)

/sbin/ldconfig

Of course you need to check that /usr/local/lib is in /etc/ld.so.conf

kind regards


Alan

P.S. As I write this, I am getting a horrible sense of doubt over
whether what I've said is correct :-) If in doubt, do man ldconfig...

-- 
Alan Fitch
(at home...)

Hi Alan:

  Yes, I had learned that LD_LIBRARY_PATH was always something of a last 
resort. I already added /usr/local/lib to ld.so.conf but still got no 
joy trying to instantiate CsoundVST. Linking it to /usr/lib also didn't 
work, but copying it to /usr/lib did, and that obviates the need for 
LD_LIBRARY_PATH. I'm not into the codebase very deeply these days, but 
if /usr/lib is hard-coded somewhere perhaps it ought not be ?

Best,

dp



Alan Peter Fitch wrote:

>On Thu, 2005-10-13 at 13:13 -0400, Dave Phillips wrote:
>  
>
>>Greetings:
>>
>>  Copying _CsoundVST.so to /usr/lib solved the problem. I'll add 
>>/usr/local/lib to LD_LIBRARY_PATH too.
>>
>>  Thanks for the help !
>>
>>    
>>
>
>Greetings from a "lurker"...
>
>I'll bet you know this Dave, but you shouldn't have to
>add /usr/local/lib to LD_LIBRARY_PATH - that's a bit of a hack. What is
>supposed to happen is that /etc/ld.so.conf contains a list of paths and
>then keeps a cache of library files. To update the cache, you should run
>(as root)
>
>/sbin/ldconfig
>
>Of course you need to check that /usr/local/lib is in /etc/ld.so.conf
>
>kind regards
>
>
>Alan
>
>P.S. As I write this, I am getting a horrible sense of doubt over
>whether what I've said is correct :-) If in doubt, do man ldconfig...
>
>  
>