All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libbdplus: Add missing libgpg arch support
Date: Tue, 5 Jul 2016 00:00:38 +0200	[thread overview]
Message-ID: <4bb56ddf-7710-31a8-e927-e67527ceefdf@gmail.com> (raw)
In-Reply-To: <1467669466-16341-1-git-send-email-maxime.hadjinlian@gmail.com>

Hi Maxime,

Le 04/07/2016 ? 23:57, Maxime Hadjinlian a ?crit :
> Thanks to Romain Naour for finding the culprit package.
> 
> Fix:
> http://autobuild.buildroot.org/results/d06/d06e3eb9ef48540b71fbec267c534523632b224f/
> 
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>

Acked-by: Romain Naour <romain.naour@gmail.com>

Best regards,
Romain

> ---
>  package/libbdplus/Config.in | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/package/libbdplus/Config.in b/package/libbdplus/Config.in
> index df5ea27..afde075 100644
> --- a/package/libbdplus/Config.in
> +++ b/package/libbdplus/Config.in
> @@ -1,5 +1,6 @@
>  config BR2_PACKAGE_LIBBDPLUS
>  	bool "libbdplus"
> +	depends on BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS # libgcrypt
>  	depends on BR2_TOOLCHAIN_HAS_THREADS
>  	depends on !BR2_STATIC_LIBS
>  	select BR2_PACKAGE_LIBGCRYPT
> @@ -15,4 +16,5 @@ config BR2_PACKAGE_LIBBDPLUS
>  	  http://www.videolan.org/developers/libbdplus.html
>  
>  comment "libbdplus needs a toolchain w/ threads, dynamic library"
> -	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
> +	depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS || \
> +		!BR2_PACKAGE_LIBGPG_ERROR_ARCH_SUPPORTS
> 

  reply	other threads:[~2016-07-04 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 21:57 [Buildroot] [PATCH] package/libbdplus: Add missing libgpg arch support Maxime Hadjinlian
2016-07-04 22:00 ` Romain Naour [this message]
2016-07-05  7:23 ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2016-07-04 21:42 Maxime Hadjinlian

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=4bb56ddf-7710-31a8-e927-e67527ceefdf@gmail.com \
    --to=romain.naour@gmail.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.