All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT
Date: Thu, 24 Nov 2011 15:09:05 +0100	[thread overview]
Message-ID: <20111124150905.40405e14@skate> (raw)
In-Reply-To: <20111124134059.5A2918F66D@busybox.osuosl.org>

Le Thu, 24 Nov 2011 14:26:52 +0100,
Peter Korsgaard <jacmet@sunsite.dk> a ?crit :

> Fix it by introducing 2 more hidden config options:
>  - BR2_TOOLCHAIN_HAS_THREADS_DEBUG
>  - BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
> 
> The first tells us if the toolchain HAS pthreads debugging support,
> and is checked by check_uclibc_feature in helper.mk for external
> uClibc based toolchains.
> 
> The second tells us if the toolchain is ABLE TO provide pthreads
> debugging support if threads are enabled, either because it's an
> internal toolchain where we can force enable it or an external
> glibc/eglibc toolchain or uClibc with the option enabled.

I don't get why two different options are needed here. Could you expand
a bit on that ?

> +config BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
> +	default y if !BR2_TOOLCHAIN_HAS_THREADS
> +	bool
> +

I also don't get this "default y if !BR2_TOOLCHAIN_HAS_THREADS". Could
you give some details ?

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-11-24 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 13:26 [Buildroot] [git commit] gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT Peter Korsgaard
2011-11-24 14:09 ` Thomas Petazzoni [this message]
2011-11-24 14:24   ` Peter Korsgaard

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=20111124150905.40405e14@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.