public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113398] <string> no longer usable with -ffreestanding Date: Mon, 15 Jan 2024 13:12:06 +0000 [thread overview] Message-ID: <bug-113398-4-ouF8j4svoN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113398-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113398 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- In file included from /home/jwakely/gcc/13/include/c++/13.2.1/string:38, from free.cc:1: /home/jwakely/gcc/13/include/c++/13.2.1/bits/requires_hosted.h:34:4: error: #error "This header is not available in freestanding mode." 34 | # error "This header is not available in freestanding mode." | ^~~~~
next prev parent reply other threads:[~2024-01-15 13:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-15 13:10 [Bug libstdc++/113398] New: " redi at gcc dot gnu.org 2024-01-15 13:12 ` redi at gcc dot gnu.org [this message] 2024-01-15 14:06 ` [Bug libstdc++/113398] " redi at gcc dot gnu.org 2024-01-24 3:42 ` hp at gcc dot gnu.org
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-113398-4-ouF8j4svoN@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: linkBe 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).