Balazs Scheidler wrote:
I start /usr/local/bin/syslog-ng manually. When I do so I get this error message:
ld.so.1: /usr/local/bin/syslog-ng: fatal: libol.so.0: open failed: No such file or directory Killed
I can get around this (sloppy) by:
env LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib /usr/local/bin/syslog-ng
Yes, you have to either add the /usr/local/lib directory to your /etc/ld.so.conf (at least this is the file under Linux), or set the above environment variable.
The [best/only] way to fix this with Solaris is as follows:
add "-R/usr/local/lib" to the LDFLAGS in src/Makefile.
latest syslog-ngs link to libol statically, so linking to shared libraries should not be a problem any more. I am wondering how the original poster could run a dynamically linked version. (versions after 05-28 are linked statically against libol)
Putting links in /usr/lib to points to the libs in /usr/local/lib would suffice, if a recompile isn't possible, and would avoid having to ensure LD_LIBRARY_PATH got set correctly before running the binary. -Chris -- Chris Mattingly | chris.mattingly@interpath.net Systems Engineer | (919) 253-6365 [tel] Interpath Communications, Inc. | (919) 253-7780 [fax]