[Buildroot] [PATCH] shairport-sync: bump to version 3.0
Arnout Vandecappelle
arnout at mind.be
Fri Mar 10 23:08:15 UTC 2017
On 10-03-17 22:54, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 10 Mar 2017 22:22:45 +0100, Thomas Petazzoni wrote:
>
>> On Fri, 10 Mar 2017 21:41:05 +0100, Jörg Krause wrote:
>>> Support for PolarSSL is deprecated and the usage of mbedTLS is
>>> recommended, if not OpenSSL is used as crypto backend.
>>>
>>> Signed-off-by: Jörg Krause <joerg.krause at embedded.rocks>
>>> ---
>>> package/shairport-sync/Config.in | 2 +-
>>> package/shairport-sync/shairport-sync.hash | 2 +-
>>> package/shairport-sync/shairport-sync.mk | 6 +++---
>>> 3 files changed, 5 insertions(+), 5 deletions(-)
>>
>> Applied to master, thanks.
>
> And I've reverted because it causes a Config.in circular dependency:
>
> package/openssl/Config.in:1:error: recursive dependency detected!
> package/openssl/Config.in:1: symbol BR2_PACKAGE_OPENSSL is selected by BR2_PACKAGE_MBEDTLS
> package/mbedtls/Config.in:1: symbol BR2_PACKAGE_MBEDTLS is selected by BR2_PACKAGE_OPENSSL
This is due to ustream-ssl:
select BR2_PACKAGE_OPENSSL if !BR2_PACKAGE_MBEDTLS
so either the direction in ustream-ssl has to be inverted, or the one in
shairport-sync.
Regards,
Arnout
>
> Try out yourself: no such warning right before your patch at commit
> cd8e5b819ff31c96dbc7ad94c28a5ad2eb838631. And at commit
> 7670dcc43e3b023b9bd613fa464533ecde7aca70, right after your patch is
> applied, we have this Config.in warning.
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
More information about the buildroot
mailing list