[syslog-ng] [Bug 188] Syslog-ng 3.3.5.90-20120810 problems: undefined symbol and ld. so library path

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Sat Aug 18 13:12:14 CEST 2012


https://bugzilla.balabit.com/show_bug.cgi?id=188


Gergely Nagy <algernon at balabit.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |algernon at balabit.hu
         AssignedTo|bazsi at balabit.hu            |algernon at balabit.hu




--- Comment #2 from Gergely Nagy <algernon at balabit.hu>  2012-08-18 13:12:13 ---
(In reply to comment #0)
> we have encountered a couple of problems when running syslog-ng-3.3.5.90-20120810 under Fedora 17 x86_64:
> 
>  1) ld.so library path
>  2) undefined symbol: tls_context_setup_session

The second is due to afsocket-notls being compiled with ENABLE_SSL set by mistake. I saw that before, but forgot about it unfortunately. If you're shipping
both afsocket and afsocket-notls in the same package, the easy fix is to not ship the latter, only one of these will be used anyway (even if I fix the
compiling bug).

As for the library path, that's a tougher one: libsyslog-ng-crypto is not really a module, but a private shared library. The libafsocket-tls.so should have an
RPATH set to /usr/lib64/syslog-ng, that way the ld.so.conf.d/ workaround wouldn't be needed. I'm not sure whether Fedora allows RPATH, on Debian, the plugins
that link to libsyslog-ng-crypto have an RPATH set, and work fine without modifying the ld.so path.

In any case, I'd rather postpone fixing these after 3.3.6, as both problem can be worked around in a reasonable way. I'll definitely fix the undefined symbol
problem in 3.3.7, but the ld.so path is a tougher beast: to fix that properly, libsyslog-ng-crypto.so must either be installed into /usr/lib64, merged into
libsyslog-ng.so, or RPATH must be set on the modules (this is already done, but perhaps Fedora strips it?). The best would be an option at configure time that
links the contents of libsyslog-ng-crypto into libsyslog-ng - for most distributions, this would be great. But that's a change to be made in 3.4 first, and I'm
not sure I want to backport it to 3.3.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the syslog-ng mailing list