public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Jason Merrill <jason@redhat.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	 Jakub Jelinek <jakub@redhat.com>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	 Florian Weimer <fweimer@redhat.com>,
	 Peter Johansson <trojkan@gmail.com>,
	 Zack Weinberg <zack@owlfolio.org>,  Autoconf <autoconf@gnu.org>,
	 "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: configure adds -std=gnu++11 to CXX variable
Date: Wed, 29 May 2024 11:33:57 -0600	[thread overview]
Message-ID: <878qzsset6.fsf@tromey.com> (raw)
In-Reply-To: <CADzB+2kaTxO7qJyLNSkEUSg842kTh0cAEd0F5Yk-2wc2koK4fw@mail.gmail.com> (Jason Merrill's message of "Tue, 28 May 2024 14:27:28 -0400")

>>>>> "Jason" == Jason Merrill <jason@redhat.com> writes:

Jason> Thanks, though I don't think all that code needs to go;
Jason> AC_PROG_CXX_STDCXX_EDITION_TRY still looks useful for a project that
Jason> relies on features from a particular standard.  We just don't want
Jason> AC_PROG_CXX to invoke it.

I didn't read the macro but there's also config/ax_cxx_compile_stdcxx.m4.
gdb uses this to make sure C++17 is available.

Tom

  parent reply	other threads:[~2024-05-29 17:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEZXgxjf7fQNHvkA09ia8ivHEsOHVKhzvoqdq=TCNRfdFTJryA@mail.gmail.com>
     [not found] ` <aece3efd-503b-4106-99ad-e66be8b0b684@app.fastmail.com>
     [not found]   ` <00dc6e30-2e12-4b29-951b-d600097b38d0@gmail.com>
     [not found]     ` <80bf1a5a-63a3-4da4-8721-88c760243add@cs.ucla.edu>
2024-05-27 10:35       ` Florian Weimer
2024-05-27 19:04         ` Paul Eggert
2024-05-27 19:18           ` Jakub Jelinek
2024-05-28  1:50             ` Paul Eggert
2024-05-28  8:20               ` Jonathan Wakely
2024-05-28 14:35                 ` Paul Eggert
2024-05-28 15:01                   ` Jason Merrill
2024-05-28 15:02                   ` Jakub Jelinek
2024-05-28 16:44                     ` Joseph Myers
2024-05-28 16:45                     ` Paul Eggert
2024-05-28 18:27                       ` Jason Merrill
2024-05-28 20:09                         ` Paul Eggert
2024-05-29 17:33                         ` Tom Tromey [this message]
2024-05-29 17:40                           ` Jason Merrill
2024-05-28  6:23           ` Florian Weimer
2024-05-28  8:15             ` Jonathan Wakely

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=878qzsset6.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=autoconf@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=trojkan@gmail.com \
    --cc=zack@owlfolio.org \
    /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).