From: Thomas Schwinge <thomas@schwinge.name>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>, 49935@debbugs.gnu.org
Subject: bug#49935: gcc-4.8 fails to build with recent GCC versions
Date: Fri, 19 Jan 2024 09:33:28 +0100 [thread overview]
Message-ID: <87mst1en8n.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <3505131.mCAMElSiHm@popigai>
On 2021-08-07T20:07:32-0300, Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> In file included from /tmp/guix-build-gcc-4.8.5.drv-0/build/powerpc64le-unknown-linux-gnu/libstdc++-v3/include/cstdlib:72:0,
> from ../../../../gcc-4.8.5/libstdc++-v3/libsupc++/del_op.cc:38:
> /gnu/store/358n1m2c8fbn6nr1mib4racjh7wfqfmy-gcc-10.3.0/include/c++/stdlib.h:38:12: error: ‘std::abort’ has not been declared
> using std::abort;
> ^
> /gnu/store/358n1m2c8fbn6nr1mib4racjh7wfqfmy-gcc-10.3.0/include/c++/stdlib.h:39:12: error: ‘std::atexit’ has not been declared
> using std::atexit;
> ^
> [...]
This looks similar to <https://issues.guix.gnu.org/41209>
"AVR toolchain fails to build", fixed by
commit fd96ae4a709c5509f2d78af3968d64fe805ad1ef
"gnu: avr-gcc: Fix conflicting GCC headers", or
<https://issues.guix.gnu.org/41210>
"gcc-cross-sans-libc-arm-none-eabi-4.9.4-1.227977 fails to build", fixed
by commit 7f6d3f395023ff430cf8b7a981d4780698e9d132
"gnu: gcc-arm-none-eabi: Fix conflicting GCC headers".
prev parent reply other threads:[~2024-01-19 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 23:07 bug#49935: gcc-4.8 fails to build with recent GCC versions Thiago Jung Bauermann via Bug reports for GNU Guix
2021-08-07 23:23 ` bug#49935: [PATCH] gnu: gcc-4.8: Fix build with GCC 6 and later Thiago Jung Bauermann via Bug reports for GNU Guix
2024-01-19 8:33 ` Thomas Schwinge [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mst1en8n.fsf@euler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=49935@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).