Hello,
thanks for the feedback on how you solved it!
Looking at the Makefile for the module, I think it needs a combination
of checking with pkg-config for libssl and libcrypto to cover the use on
old distros.
Cheers,
Daniel
On 14/08/16 11:40, Christian Lox wrote:
> Short update:
> When changi
Short update:
When changing the module Makefile to
SSL_BUILDER=$(shell \
if pkg-config --exists libcrypto; then \
echo 'pkg-config libcrypto'; \
fi)
instead of libssl
it compiles fine and is linked against libcrypto without throwing the error.
Is this due to a chan
Hi.
Same problem here; undefined symbol : EVP_sha1 in outbound.so
pkg-config was available when compiled from source. Tried installing several
dev packages and so on but always the same error.
How do i link it against libssl/libcrypto?
Thanks,
Christian
_
g tool.
>
>
>
>
> *From:* sr-users on behalf of
> Daniel-Constantin Mierla
> *Sent:* Wednesday, July 27, 2016 6:20 AM
> *To:* Kamailio (SER) - Users Mailing List
> *Subject:* Re: [SR-Users] undefined symbol: EVP_
>From source and no, I did not installed pkg-config tool.
From: sr-users on behalf of
Daniel-Constantin Mierla
Sent: Wednesday, July 27, 2016 6:20 AM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] undefined symbol: EVP_sha1 when using outbo
Hello,
so it is not linked against libssl/libcrypto.
Did you installed from packages or from sources? If later, do you have
pkg-config tool installed?
Cheers,
Daniel
On 26/07/16 18:40, Francisco Burgos wrote:
>
> this is the output of the command
>
> sudo ldd ../lib64/kamailio/modules/outbo
this is the output of the command
sudo ldd ../lib64/kamailio/modules/outbound.so
linux-vdso.so.1 => (0x7fff0a9e2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd869171000)
/lib64/ld-linux-x86-64.so.2 (0x55aba6816000)
If im not mistaken the linking between the cr
Hello,
you should see which module throws this error -- the log messages above
or below the one you mentioned here provides more details.
Once you are sure which module has the undefined symbol, then just do:
ldd /path/to/the/module.so
and send the output here.
Cheers,
Daniel
On 21/07/1