From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gdb: add support for gdb 8.0
Date: Tue, 13 Jun 2017 23:37:23 +0200 [thread overview]
Message-ID: <87d1a7bmcs.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170612093640.0b2da648@windsurf.home> (Thomas Petazzoni's message of "Mon, 12 Jun 2017 09:36:40 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hello,
> On Sun, 11 Jun 2017 23:17:36 +0200, Arnout Vandecappelle wrote:
>> > Applied to master, thanks. Do you intend to send a patch that updates
>> > the default gdb version to 7.12, and drop support for 7.10 ?
>>
>> Since we've been discussing version dropping, perhaps it's time to consider gdb
>> as well.
>>
>> Is there really any reason to support multiple versions of gdb?
>>
>> If yes, is there a reason to not use the latest version as default?
>>
>> And the same questions for binutils.
> All this version selection stuff is very historical. I guess one reason
> for it is to allow people to upgrade Buildroot while keeping the same
> toolchain components, which are often quite sensitive to changes.
> That's the main reasoning.
Indeed. People should normally not use the internal toolchain support
(E.G. rebuilding the toolchain every time) for real projects, but
yeah. You can still reuse a toolchain built with an older BR version,
but you naturally don't get any of the new fixes.
With that said, our internal toolchain component version options do make
it unrealistic for us to really test all combinations, so gradually
limiting the number of supported versions going forward is probably the
way to go.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-06-13 21:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 20:46 [Buildroot] [PATCH] package/gdb: add support for gdb 8.0 Romain Naour
2017-06-11 16:10 ` Thomas Petazzoni
2017-06-11 21:17 ` Arnout Vandecappelle
2017-06-12 7:36 ` Thomas Petazzoni
2017-06-12 8:19 ` Arnout Vandecappelle
2017-06-13 21:37 ` 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=87d1a7bmcs.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.