public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arsen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/115907] Libstdc++ and GCC itself should avoid glibc above 2.34 dependency
Date: Sat, 13 Jul 2024 13:17:14 +0000	[thread overview]
Message-ID: <bug-115907-4-nGqUIqm6RM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115907-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115907

--- Comment #20 from Arsen Arsenović <arsen at gcc dot gnu.org> ---
(In reply to cqwrteur from comment #17)
> Then why? Why does it define _ISOC2X_SOURCE? C++ is not even C.

"it"?  presuming you mean glibc, because _GNU_SOURCES enables all features,
including the C2X specific ones.

note that not enabling those would not fix downgrading being broken.

  parent reply	other threads:[~2024-07-13 13:17 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13 11:55 [Bug libstdc++/115907] New: " unlvsur at live dot com
2024-07-13 12:13 ` [Bug libstdc++/115907] " unlvsur at live dot com
2024-07-13 12:39 ` pinskia at gcc dot gnu.org
2024-07-13 12:41 ` pinskia at gcc dot gnu.org
2024-07-13 12:56 ` unlvsur at live dot com
2024-07-13 12:57 ` unlvsur at live dot com
2024-07-13 12:59 ` pinskia at gcc dot gnu.org
2024-07-13 13:04 ` unlvsur at live dot com
2024-07-13 13:04 ` unlvsur at live dot com
2024-07-13 13:05 ` unlvsur at live dot com
2024-07-13 13:05 ` unlvsur at live dot com
2024-07-13 13:06 ` unlvsur at live dot com
2024-07-13 13:08 ` unlvsur at live dot com
2024-07-13 13:10 ` unlvsur at live dot com
2024-07-13 13:11 ` pinskia at gcc dot gnu.org
2024-07-13 13:12 ` arsen at gcc dot gnu.org
2024-07-13 13:13 ` pinskia at gcc dot gnu.org
2024-07-13 13:13 ` unlvsur at live dot com
2024-07-13 13:14 ` unlvsur at live dot com
2024-07-13 13:15 ` pinskia at gcc dot gnu.org
2024-07-13 13:17 ` arsen at gcc dot gnu.org [this message]
2024-07-13 13:19 ` unlvsur at live dot com
2024-07-13 13:20 ` unlvsur at live dot com
2024-07-13 13:21 ` pinskia at gcc dot gnu.org
2024-07-13 13:23 ` unlvsur at live dot com
2024-07-13 13:31 ` pinskia at gcc dot gnu.org
2024-07-13 13:37 ` unlvsur at live dot com
2024-07-13 13:41 ` pinskia at gcc dot gnu.org
2024-07-13 13:43 ` arsen at gcc dot gnu.org
2024-07-13 14:01 ` unlvsur at live dot com
2024-07-13 14:06 ` unlvsur at live dot com
2024-07-13 14:10 ` unlvsur at live dot com
2024-07-13 14:12 ` unlvsur at live dot com
2024-07-13 14:23 ` unlvsur at live dot com
2024-07-13 14:47 ` arsen at gcc dot gnu.org
2024-07-13 15:51 ` unlvsur at live dot com
2024-07-13 15:55 ` unlvsur at live dot com
2024-07-13 19:30 ` pinskia at gcc dot gnu.org
2024-07-13 19:57 ` arsen at gcc dot gnu.org
2024-07-13 20:10 ` unlvsur at live dot com
2024-07-13 20:12 ` pinskia at gcc dot gnu.org
2024-07-19 18:55 ` frankhb1989 at gmail dot com
2024-07-19 19:02 ` pinskia at gcc dot gnu.org
2024-07-21 14:31 ` unlvsur at live dot com
2024-07-21 14:35 ` unlvsur at live dot com
2024-07-21 14:36 ` pinskia at gcc dot gnu.org
2024-07-21 14:38 ` unlvsur at live dot com
2024-07-21 14:57 ` pinskia at gcc dot gnu.org
2024-07-21 15:01 ` arsen at gcc dot gnu.org
2024-07-21 15:13 ` unlvsur at live dot com
2024-07-21 15:14 ` unlvsur at live dot com
2024-07-21 15:15 ` unlvsur at live dot com
2024-07-21 15:16 ` unlvsur at live dot com
2024-07-21 15:17 ` unlvsur at live dot com
2024-07-21 15:18 ` unlvsur at live dot com
2024-07-21 15:20 ` pinskia at gcc dot gnu.org
2024-07-21 15:21 ` unlvsur at live dot com
2024-07-21 15:53 ` arsen at gcc dot gnu.org
2024-07-22  9:41 ` redi at gcc dot gnu.org
2024-07-22  9:53 ` unlvsur at live dot com
2024-07-22  9:56 ` unlvsur at live dot com

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=bug-115907-4-nGqUIqm6RM@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).