https://bugzilla.balabit.com/show_bug.cgi?id=214 Tamás Pál <folti@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |folti@balabit.hu --- Comment #4 from Tamás Pál <folti@balabit.hu> 2012-12-28 00:09:02 --- (In reply to comment #2)
(In reply to comment #1)
Also to note, version 3.2.5 does not have any issues with lib/syslog-ng/libafsocket.so dependencies... the ldd output doesn't seem to indicate a requirement for libsyslog-ng-crypto.
libsyslog-ng-crypto was split out of libsyslog-ng in 3.3.
My guess is that libsyslog-ng-crypto gets installed into /opt/local/syslogng/lib/syslog-ng/, which is not on the dynamic loader's path, and the AIX linker thingies do not support RPATH. Yes, yes and no. AIX linker supports RPATH, but by default, it's set to /usr/lib:/lib (or whatever libtool set's it under the hood) you can set your own one by adding something like this to LDFLAGS when running configure: -Wl,-bnolibpath,-blibpath:/opt/local/syslogng/lib:/opt/local/syslogng/lib/syslog-ng:/usr/lib:/lib
The best course of action here would be to link libsyslog-ng-crypto directly into libsyslog-ng, I believe. Or, move it out of lib/syslog-ng, into lib/ itself.
PE does the second, with setting --modulepath to --libpath too. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.