[syslog-ng] syslog-ng 3.3.5 and openssl

[Balazs Scheidler]

Hi,

Thanks for reporting this, I've committed a patch to fix this issue.

commit 198e350545c718cb3afd9321a033216a67d1d34b
Author: Balazs Scheidler <bazsi at balabit.hu>
Date:   Tue May 1 14:09:33 2012 +0200

    libsyslog-ng-crypto.so: link against libcrypto explicitly
    
    This patch adds OPENSSL_LIBS to LIBADD so that libsyslog-ng-crypto.so is
    always linked against libcrypto.so
    
    Reported-By: Alexander Komyagin <komyagin at altell.ru>
    Signed-off-by: Balazs Scheidler <bazsi at balabit.hu>


On Fri, 2012-04-27 at 12:02 +0400, Alexander Komyagin wrote:
> Hi! I noticed that when I'm compiling syslog-ng 3.3.5 with openssl
> enabled (at least in my environment), libsyslog-ng-crypto.so somehow is
> not linked with libssl (checked with ldd), thus resulting with
> unresolved symbols error on syslog-ng startup for afsocket module.
> Attached patch fixes the issue.
> 
> 
> --- syslog-ng-3.3.5.orig/lib/Makefile.am	2012-03-31 22:23:43.000000000
> +0400
> +++ syslog-ng-3.3.5/lib/Makefile.am	2012-04-26 17:32:58.000000000 +0400
> @@ -12,7 +12,7 @@
>  libsyslog_ng_la_LDFLAGS = -no-undefined -release @VERSION@
>  
>  module_LTLIBRARIES = libsyslog-ng-crypto.la
> -libsyslog_ng_crypto_la_LIBADD = @CORE_DEPS_LIBS@ libsyslog-ng.la
> +libsyslog_ng_crypto_la_LIBADD = @CORE_DEPS_LIBS@ @OPENSSL_LIBS@
> libsyslog-ng.la
>  libsyslog_ng_crypto_la_LDFLAGS = -no-undefined -avoid-version
>  
>  # this is intentionally formatted so conflicts are less likely to
> arise. one name in every line.
> 

-- 
Bazsi