public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104080] [12 Regression] newlib doesn't have endian.h causing build failure with 2800bc08e4ab r12-6646
Date: Tue, 18 Jan 2022 11:58:04 +0000 [thread overview]
Message-ID: <bug-104080-4-x95JBG7IPW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104080-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104080
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #8 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #7)
> This should be fixed now.
Confirmed (autotester has completed a build at r12-6665-g8f6b62e0f0c9).
Closing.
Thanks!
prev parent reply other threads:[~2022-01-18 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 2:10 [Bug libstdc++/104080] New: " hp at gcc dot gnu.org
2022-01-18 2:12 ` [Bug libstdc++/104080] " hp at gcc dot gnu.org
2022-01-18 2:13 ` hp at gcc dot gnu.org
2022-01-18 2:58 ` hp at gcc dot gnu.org
2022-01-18 2:58 ` hp at gcc dot gnu.org
2022-01-18 7:30 ` rguenth at gcc dot gnu.org
2022-01-18 9:27 ` pexu@gcc-bugzilla.mail.kapsi.fi
2022-01-18 9:31 ` redi at gcc dot gnu.org
2022-01-18 9:39 ` redi at gcc dot gnu.org
2022-01-18 9:55 ` cvs-commit at gcc dot gnu.org
2022-01-18 10:04 ` cvs-commit at gcc dot gnu.org
2022-01-18 10:09 ` redi at gcc dot gnu.org
2022-01-18 11:58 ` hp at gcc dot gnu.org [this message]
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-104080-4-x95JBG7IPW@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).