From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/asterisk: libsrtp needs openssl
Date: Thu, 4 Oct 2018 14:18:56 +0200 [thread overview]
Message-ID: <20181004141856.3e7a32b6@windsurf> (raw)
In-Reply-To: <20181003190829.28477-1-bernd.kuhls@t-online.de>
Hello,
On Wed, 3 Oct 2018 21:08:29 +0200, Bernd Kuhls wrote:
> Fixes configure error
>
> checking for the ability of -lsrtp2 to be linked in a shared object... yes
> checking for srtp_crypto_policy_set_aes_cm_256_hmac_sha1_80 in -lsrtp2... yes
> checking for srtp_crypto_policy_set_aes_cm_192_hmac_sha1_80 in -lsrtp2... no
> checking for srtp_crypto_policy_set_aes_gcm_128_8_auth in -lsrtp2... no
> checking for srtp_shutdown in -lsrtp2... yes
> checking for srtp2/srtp.h... (cached) yes
> configure: WARNING: ***
> configure: WARNING: *** OpenSSL required when using libsrtp2, checking for libsrtp instead.
> configure: WARNING: ***
>
> using this defconfig:
>
> BR2_PACKAGE_LIBSRTP=y
> BR2_PACKAGE_ASTERISK=y
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/asterisk/asterisk.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/asterisk/asterisk.mk b/package/asterisk/asterisk.mk
> index 9480d6ba82..c3f1136068 100644
> --- a/package/asterisk/asterisk.mk
> +++ b/package/asterisk/asterisk.mk
> @@ -245,7 +245,8 @@ else
> ASTERISK_CONF_OPTS += --without-speex --without-speexdsp
> endif
>
> -ifeq ($(BR2_PACKAGE_LIBSRTP),y)
> +# asterisk needs an openssl-enabled libsrtp
> +ifeq ($(BR2_PACKAGE_LIBSRTP)$(BR2_PACKAGE_OPENSSL)x$(BR2_STATIC_LIBS),yyx)
Any reason to exclude static linking configurations here? This is not
explained in the commit log.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-04 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 19:08 [Buildroot] [PATCH 1/1] package/asterisk: libsrtp needs openssl Bernd Kuhls
2018-10-04 12:18 ` Thomas Petazzoni [this message]
2018-10-04 17:56 ` Bernd Kuhls
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181004141856.3e7a32b6@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.