Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT
Date: Thu, 24 Nov 2011 15:24:58 +0100	[thread overview]
Message-ID: <87ipm9a98l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20111124150905.40405e14@skate> (Thomas Petazzoni's message of "Thu, 24 Nov 2011 15:09:05 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

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

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

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

I tried to do so in the commit message - But I'll give it another try.

We need 2 things:

- An option to test in helper.mk when we use external uClibc based
  toolchains

- Something to ensure you cannot enable the effected GDB versions with
  incompatible toolchains

Those two things are not the same (E.G. if you don't have threads
support then you can use the new GDB versions without thread
debugging). The 2nd (_IF_NEEDED) option is not strictly needed, you
could also just write out the complicated logic for each GDB 7.x
version, but that's kind of ugly and I had some problems getting kconfig
to handle it, so I added the helper option instead.

I hope this helps, otherwise just ask.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2011-11-24 14:24 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
2011-11-24 14:24   ` Peter Korsgaard [this message]

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=87ipm9a98l.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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