public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/103305] [12 Regression] Cannot build C++ with newlib on aarch64-none-elf or bfin-elf
Date: Wed, 17 Nov 2021 18:01:29 +0000	[thread overview]
Message-ID: <bug-103305-4-pquN6H2vJB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103305-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
logs indicate that this started happening between 
3ba1bd0d9dbc..2ec453b566ac on Nov 12. However that range contains a suspicious
newlib commit
https://github.com/bminor/newlib/commit/3ba1bd0d9dbc015c14a0aaafcef042f706d1249a
which changed ctype_.h.  So that is likely the culprid.

  parent reply	other threads:[~2021-11-17 18:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 16:07 [Bug bootstrap/103305] New: [12 Regression] Cannot build aarch64-none-elf tnfchris at gcc dot gnu.org
2021-11-17 16:34 ` [Bug bootstrap/103305] [12 Regression] Cannot build C++ with newlib on aarch64-none-elf or bfin-elf aldyh at gcc dot gnu.org
2021-11-17 17:19 ` redi at gcc dot gnu.org
2021-11-17 18:01 ` tnfchris at gcc dot gnu.org [this message]
2021-11-17 18:05 ` tnfchris at gcc dot gnu.org
2021-11-17 18:26 ` redi at gcc dot gnu.org
2021-11-17 18:31 ` redi at gcc dot gnu.org
2021-11-18  8:36 ` [Bug libstdc++/103305] Cannot build libstdc++ with newlib on aarch64-none-elf or bfin-elf with new version of newlib tnfchris at gcc dot gnu.org
2021-11-18 15:02 ` tnfchris at gcc dot gnu.org
2021-11-18 15:51 ` redi at gcc dot gnu.org
2021-11-18 15:53 ` tnfchris at gcc dot gnu.org
2021-11-19  8:48 ` cvs-commit at gcc dot gnu.org
2021-11-19  8:52 ` tnfchris at gcc dot gnu.org
2021-11-19  9:02 ` redi at gcc dot gnu.org
2021-11-20 14:55 ` pexu@gcc-bugzilla.mail.kapsi.fi
2021-11-20 15:52 ` redi at gcc dot gnu.org
2021-11-23 10:57 ` redi at gcc dot gnu.org
2021-11-23 10:59 ` redi at gcc dot gnu.org
2021-11-23 11:01 ` redi at gcc dot gnu.org
2021-11-23 11:07 ` redi at gcc dot gnu.org
2021-11-30 11:24 ` tnfchris at gcc dot gnu.org
2021-12-03 11:55 ` rearnsha at gcc dot gnu.org
2021-12-06  9:28 ` tnfchris at gcc dot gnu.org
2021-12-06 10:45 ` redi at gcc dot gnu.org
2021-12-07 10:46 ` cvs-commit at gcc dot gnu.org
2021-12-07 10:47 ` tnfchris 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-103305-4-pquN6H2vJB@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).