Speech Dispatcher and Ldconfig
Steve Holmes
steve at holmesgrown.com
Sat Jan 19 00:01:31 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
I don't know about ldconfig but do realize that many programs' lib
modules get found automatically whenever an ldconfig is run. In most
cases, these libraries are in /usr/lib or /usr/local/lib. When Speech
Dispatcher is compiled directly onto a machine, this all seems to work
fine. But when I built a binary Slackware package and subsequently
install that package onto a machine, the libs get placed in their
proper directories and all, but when I run speech-dispatcher, it can't
find the libraries. When I did an 'ldconfig -v', the
speech-dispatcher libs didn't show up either. But if I add
/usr/lib/speech-dispatcher to ld.so.conf, then 'ldconfig -v' shows the
library and dispatcher works fine.
What I'm wondering is why the difference and when does one really have
to add additional points to ld.so.conf? I thought all that would be
automatic. I want the installation of these packages to go as
seemlessly as possible for the less experienced user who might not
think to mess with ldconfig.
Any ideas?
- --
HolmesGrown Solutions
The best solutions for the best price!
http://holmesgrown.ld.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHkS/LWSjv55S0LfERA4AMAJoDTJxj9U7HyJp63n/2ks9R3WXS0gCg0yPU
za5DFHwkMoPFn1eRS8xmWsc=
=qtEu
-----END PGP SIGNATURE-----
More information about the Speechd
mailing list