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 c++/107781] strchrnul' was not declared in this scope; did you mean 'strchr'? For contracts for canadian compilation
Date: Mon, 21 Nov 2022 10:35:30 +0000 [thread overview]
Message-ID: <bug-107781-4-820AEMNH6r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107781-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107781
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-11-21
Ever confirmed|0 |1
Keywords| |build
Status|UNCONFIRMED |NEW
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
https://gcc.gnu.org/pipermail/gcc/2022-November/240070.html
Fails for macOS too. Probably others, as strchrnul is glibc-specific.
next prev parent reply other threads:[~2022-11-21 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 7:25 [Bug c++/107781] New: " unlvsur at live dot com
2022-11-21 9:13 ` [Bug c++/107781] " schwab@linux-m68k.org
2022-11-21 10:35 ` redi at gcc dot gnu.org [this message]
2022-11-21 14:01 ` dje at gcc dot gnu.org
2022-11-21 22:44 ` jason at gcc dot gnu.org
2022-11-22 10:58 ` redi at gcc dot gnu.org
2022-11-22 11:01 ` jakub at gcc dot gnu.org
2022-11-22 11:04 ` jakub at gcc dot gnu.org
2022-11-22 14:30 ` cvs-commit at gcc dot gnu.org
2022-11-22 14:47 ` jason at gcc dot gnu.org
2022-11-28 22:38 ` [Bug c++/107781] [13 Regression] " pinskia 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-107781-4-820AEMNH6r@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).