From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] shairport-sync: fix static link with mbedtls
Date: Tue, 5 Sep 2017 21:44:47 +0200 [thread overview]
Message-ID: <20170905214447.7e75c2da@windsurf.lan> (raw)
In-Reply-To: <87aa32f0dbacc3252ade43fc605e7f2c310e6465.1504638326.git.baruch@tkos.co.il>
Hello,
On Tue, 5 Sep 2017 22:05:25 +0300, Baruch Siach wrote:
> # Avahi or tinysvcmdns (shaiport-sync bundles its own version of tinysvcmdns).
> # Avahi support needs libavahi-client, which is built by avahi if avahi-daemon
> # and dbus is selected. Since there is no BR2_PACKAGE_LIBAVAHI_CLIENT config
> @@ -38,6 +40,10 @@ SHAIRPORT_SYNC_CONF_OPTS += --with-ssl=openssl
> else
> SHAIRPORT_SYNC_DEPENDENCIES += mbedtls
> SHAIRPORT_SYNC_CONF_OPTS += --with-ssl=mbedtls
> +SHAIRPORT_SYNC_CONF_LIBS += -lmbedx509 -lmbedcrypto
> +ifeq ($(BR2_PACKAGE_MBEDTLS_COMPRESSION),y)
> +SHAIRPORT_SYNC_CONF_LIBS += -lz
> +endif
> endif
This is crazy. Can we submit a mbedtls patch adding a pkg-config file ?
They are open to it it seems:
https://github.com/ARMmbed/mbedtls/issues/228. Of course,
shairport-sync would have to be modified to use it.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-09-05 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 19:05 [Buildroot] [PATCH 1/2] shairport-sync: fix static link with mbedtls Baruch Siach
2017-09-05 19:05 ` [Buildroot] [PATCH 2/2] mbedtls: security bump to version 2.6.0 Baruch Siach
2017-09-07 9:18 ` Peter Korsgaard
2017-09-07 13:15 ` Peter Korsgaard
2017-09-05 19:44 ` Thomas Petazzoni [this message]
2017-09-06 5:30 ` [Buildroot] [PATCH 1/2] shairport-sync: fix static link with mbedtls Baruch Siach
2017-09-24 11:52 ` Arnout Vandecappelle
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=20170905214447.7e75c2da@windsurf.lan \
--to=thomas.petazzoni@free-electrons.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.