public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>
Subject: Re: [RFC] [gdb/build] Require c++17 compiler
Date: Thu, 05 Oct 2023 09:31:07 -0600	[thread overview]
Message-ID: <87edi9xf0k.fsf@tromey.com> (raw)
In-Reply-To: <20231005065449.32643-1-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Thu, 5 Oct 2023 08:54:49 +0200")

>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:

Tom> A review of some relevant distros has shown that in case that requiring c++17
Tom> results in no longer being able to use the system compiler, an alternative,
Tom> newer compiler that does support c++17 is readily available.

Tom> With nothing holding back the change, require a c++17 compiler to build gdb.

I'm in favor of the change.

IIRC the current rule is that gdb shouldn't rely on anything newer than
3 years old (?) and furthermore that the required compiler should either
be in the major distros' active LTS releases, or readily installable
there.  Since you've looked into this, I think we're fine to move
forward.

However, I do agree with Lancelot that we should do this in GDB 15.
That is, hold this patch and land it on trunk shortly after the branch
is made.

thanks,
Tom

  parent reply	other threads:[~2023-10-05 15:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  6:54 Tom de Vries
2023-10-05 10:33 ` [PATCH RFC] " Lancelot SIX
2023-10-05 12:26   ` Andrew Burgess
2023-10-05 14:26     ` Lancelot SIX
2023-10-05 14:32       ` Simon Marchi
2023-10-05 14:55         ` Lancelot SIX
2023-10-09 14:32           ` Andrew Burgess
2023-10-05 15:55         ` Tom Tromey
2023-10-12 17:30   ` Pedro Alves
2023-10-05 15:31 ` Tom Tromey [this message]
2023-10-10 17:39   ` [RFC] [gdb/build] " Tom Tromey
2023-10-10 19:16     ` Simon Marchi
2023-10-12 17:10 ` Pedro Alves
2023-10-12 17:22 ` Pedro Alves

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=87edi9xf0k.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).