Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] shairport-sync: bump to version 3.0
Date: Fri, 10 Mar 2017 22:54:34 +0100	[thread overview]
Message-ID: <20170310225434.45202999@free-electrons.com> (raw)
In-Reply-To: <20170310222245.2494cd18@free-electrons.com>

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@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

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
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-10 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 20:41 [Buildroot] [PATCH] shairport-sync: bump to version 3.0 Jörg Krause
2017-03-10 21:22 ` Thomas Petazzoni
2017-03-10 21:54   ` Thomas Petazzoni [this message]
2017-03-10 23:08     ` 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=20170310225434.45202999@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox