Hi all,

After a clean build from sources, i installed Csound and all files
(libraries, tcl, java). I can launch it, but get :

bash-3.00# csound
Localisation of messages is disabled, using default language.
time resolution is 1000.000 ns
WARNING: could not open library '/usr/pkg/lib/csound/plugins/libampmidid.so'
(-1)
WARNING: could not open library '/usr/pkg/lib/csound/plugins/libbabo.so'
(-1)
WARNING: could not open library '/usr/pkg/lib/csound/plugins/libbarmodel.so'
(-1)
WARNING: could not open library '/usr/pkg/lib/csound/plugins/libcompress.so'
(-1)
WARNING: could not open library '/usr/pkg/lib/csound/plugins/libdate.so'
(-1)

(and all plugins).

- my OPCODEDIR is set as well and recognized (not error message about that).
- the plugins are all in 755 mode, also in the pathes.
- assuming that i works in 64 bits, i verified with ldd and ld_debug that
the main executable csound finds all its required system libraries.

What can mean this "(-1)" ? I builded csound with only the default options,
but it recognized as well my installed Jack, and other hand it builded
itself all plugins.

I don't have yet Portaudio installed, assuming i intend to use Jack (OSS).
I'll make that, as try, but what can that have to see with the plugins
problem ?

- I posted a time in the Sourceforge forum, but after some tries and
reflexions i have no idea about what happens. Other hand, it seems that i'm
the only one with this kind of issue. Strange...

(Of course, same problem using Blue)

Best regards,

Sergio





-- 
View this message in context: http://www.nabble.com/Plugins-tp15949384p15949384.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi!
   Probably nothing much.. But anyway, Recheck the following:
1. The environment variable OPCODEDIR is properly set. On my system, although 
32BIT, it points to:
OPCODEDIR=/usr/local/lib/csound/plugins64
   That's where I find directly: libampmidi.so lib babo.so etc.
2. If this is the case - you said something like it -, try running:
ldconfig
3. Is this /usr/pkg/ directory in your usual path. I'm sure you can run 
programs not in the standard path, but I simply wonder, because it's usually 
just /usr/lib or /usr/local/lib...
4. Have another look at the scons -h output when building csound, there is 
something about dynamiclibraries or dynamicplugins, be sure to explicitly makr 
them.
   All I could think off, having had something similar once... HTH.
   Kindest regards
         Julien

--------
Music was my first love and it will be my last (John Miles)

======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de

Hi Steven,

What Linux are you using?

- Solaris x86-64 : not Linux, but also not very different in this kind of
problems. 

 I'm wondering if SELinux is enabled or some
other kind of security system, which I've experienced sometimes messes
with library loading.

- really good idea, also i suspects some trivial reason for this issue.

Best regards,

Sergio 
-- 
View this message in context: http://www.nabble.com/Plugins-tp15949384p15951928.html
Sent from the Csound - General mailing list archive at Nabble.com.

1. The environment variable OPCODEDIR is properly set. On my system,
although 
32BIT, it points to:
OPCODEDIR=/usr/local/lib/csound/plugins64

Yes, properly set : install.py decided /plugins, not /plugins64, because the
build itself. Trying /plugins64, i get an error message, but not with
/plugins.
 
2. If this is the case - you said something like it -, try running:
ldconfig

Not necessary (and impossible) under Solaris. And Csound finds as well all
the required system libraries, only with the plugins i have the issue.

3. Is this /usr/pkg/ directory in your usual path. I'm sure you can run 
programs not in the standard path, but I simply wonder, because it's usually 
just /usr/lib or /usr/local/lib...

I tried both /usr/local and /usr/pkg : same result. Finally i opted for
/usr/pkg, where i have my Python 64 bits. It's not a real reason, but why
not...

4. Have another look at the scons -h output when building csound, there is 
something about dynamiclibraries or dynamicplugins, be sure to explicitly
makr 
them.

OK : i'll make that (and report after).

Thank's greatly !

Sergio
-- 
View this message in context: http://www.nabble.com/Plugins-tp15949384p15971257.html
Sent from the Csound - General mailing list archive at Nabble.com.