All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libcap-ng: doesn't build on AVR32, requires TLS support
Date: Sun, 6 Oct 2013 23:23:44 +0200	[thread overview]
Message-ID: <20131006232344.493a4ebc@skate> (raw)
In-Reply-To: <871u3yfddd.fsf@dell.be.48ers.dk>

Dear Peter Korsgaard,

On Sun, 06 Oct 2013 20:44:30 +0200, Peter Korsgaard wrote:

>  Thomas> diff --git a/package/libcap-ng/Config.in b/package/libcap-ng/Config.in
>  Thomas> index d1663cd..b799dc9 100644
>  Thomas> --- a/package/libcap-ng/Config.in
>  Thomas> +++ b/package/libcap-ng/Config.in
>  Thomas> @@ -1,5 +1,7 @@
>  Thomas>  config BR2_PACKAGE_LIBCAP_NG
>  Thomas>  	bool "libcap-ng"
>  Thomas> +	# tls support, needed by libcap-ng, not available on avr32
>  Thomas> +	depends on !BR2_avr32
> 
> Shouldn't it then depend on BR2_GCC_ENABLE_TLS (and the avr32 toolchain
> not select it)?

It wouldn't work with external toolchains, which is the reason why I
excluded the AVR32 architecture rather than using a BR2_GCC_ENABLE_TLS
condition.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-10-06 21:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 16:34 [Buildroot] [PATCH] libcap-ng: doesn't build on AVR32, requires TLS support Thomas Petazzoni
2013-10-06 18:44 ` Peter Korsgaard
2013-10-06 21:23   ` Thomas Petazzoni [this message]
2013-10-06 21:42     ` Peter Korsgaard
2013-10-07  6:53       ` Thomas Petazzoni

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=20131006232344.493a4ebc@skate \
    --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.