From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gdb: adjust behavior when thread debug is not available
Date: Thu, 17 May 2012 23:54:06 +0200 [thread overview]
Message-ID: <87wr4ao4n5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1337263520-5865-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Thu, 17 May 2012 16:05:20 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> When an external toolchain without thread debug is used, the gdb
Thomas> package can be selected, but no version can be choosen, since none
Thomas> match any of the requirements. This leads Buildroot to try to build
Thomas> gdb for the target without a version being defined, as in the
Thomas> following build log:
Thomas> http://autobuild.buildroot.org/results/84e8fd2df0cc22448052a572c2e9a6e03dd137eb/build-end.log
Thomas> To fix this, we adjust the dependencies of the BR2_PACKAGE_GDB option
Thomas> so that the package as a whole is not selectable when the required
Thomas> conditions are not met. Basically, we have the choice of:
Thomas> * Having a toolchain that supports thread debugging, which is needed
Thomas> for gdb >= 7.x
Thomas> * Having BR2_DEPRECATED enabled, which allows gdb 6.8 to be selected,
Thomas> which doesn't require thread debugging
Thomas> * Using either avr32 of bfin, since those architectures have special
Thomas> old gdb versions
Thanks, but this conflicts with your recent 'gdb: not available on
avr32' patch. Looking at that patch it seems you can drop the avr32
handling.
Care to fix and resend?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-05-17 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 14:05 [Buildroot] [PATCH] gdb: adjust behavior when thread debug is not available Thomas Petazzoni
2012-05-17 21:54 ` Peter Korsgaard [this message]
2012-05-18 6:21 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2012-06-02 16:39 Thomas Petazzoni
2012-11-03 16:54 ` 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=87wr4ao4n5.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