public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Helmut Zeisel <HZ2012@gmx.at>
Cc: gcc@gcc.gnu.org
Subject: Re: Aw: Re: GCC 13.1 compile error when using CXXFLAGS=-std=c++20
Date: Thu, 27 Apr 2023 11:40:39 +0200	[thread overview]
Message-ID: <ZEpDFyAXbt63plXA@tucnak> (raw)
In-Reply-To: <trinity-c5e99dbf-4510-4bd1-af4d-6ae6d409e373-1682588123829@3c-app-gmx-bap68>

On Thu, Apr 27, 2023 at 11:35:23AM +0200, Helmut Zeisel wrote:
> >Von: "Jakub Jelinek" <jakub@redhat.com>
> >An: "Helmut Zeisel" <HZ2012@gmx.at>
> >Cc: gcc@gcc.gnu.org
> >Betreff: Re: GCC 13.1 compile error when using CXXFLAGS=-std=c++20
> >On Thu, Apr 27, 2023 at 11:09:19AM +0200, Helmut Zeisel via Gcc wrote:
> >> I compiled GCC 13.1.0 with GCC 12 and had the environment variable CXXFLAGS set to -std=c++20
> >> This gives the error (both linux and cygin)
> >>
> >> gcc-13.1.0/libstdc++-v3/src/c++98/bitmap_allocator.cc:51:23: error: ISO C++17 does not allow dynamic exception specifications
> >> 51 | _M_get(size_t __sz) throw(std::bad_alloc)
> >>
> >> After
> >>
> >> unset CXXFLAGS
> >>
> >> compilation works
> 
> >Don't do it. 
> 
> Dont do *what*?
> export CXXFLAGS=... ?

Include explicit -std= settings in such exported variables, especially when
building GCC.  Packages should decide themselves in which language version
they are written in, or if they are written in common subset, they should
just defer to the compiler default.
Note, doing that would break building even much older GCC versions.

> unset CXXFLAGS ?
> Compile GCC 13 with GCC 12?

	Jakub


  reply	other threads:[~2023-04-27  9:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  9:09 Helmut Zeisel
2023-04-27  9:22 ` Jakub Jelinek
2023-04-27  9:35   ` Aw: " Helmut Zeisel
2023-04-27  9:40     ` Jakub Jelinek [this message]
2023-05-08  8:38       ` NightStrike
2023-05-08  8:51         ` 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=ZEpDFyAXbt63plXA@tucnak \
    --to=jakub@redhat.com \
    --cc=HZ2012@gmx.at \
    --cc=gcc@gcc.gnu.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).