public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/98412] libcody does not compile with older GCC versions Date: Mon, 21 Dec 2020 17:20:21 +0000 [thread overview] Message-ID: <bug-98412-4-4N6u3DbTzR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98412 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nathan Sidwell <nathan@gcc.gnu.org>: https://gcc.gnu.org/g:1467a5c5ab0dfbae3175b4a326467f939864dadb commit r11-6289-g1467a5c5ab0dfbae3175b4a326467f939864dadb Author: Nathan Sidwell <nathan@acm.org> Date: Mon Dec 21 09:16:48 2020 -0800 bootstrap: std:stoul non-portable [PR 98412] Fix some more system-specific issues. Not everyone's C++11 is the same :( PR bootstrap/98412 libcody/ * client.cc: Include cstdlib. * server.cc: Include cstdlib. gcc/cp/ * mapper-client.cc: INCLUDE_STRING, INCLUDE_VECTOR. (module_client::open_module_client): Avoid std::stoul. * mapper-resolver.cc: INCLUDE_STRING, INCLUDE_VECTOR.
next prev parent reply other threads:[~2020-12-21 17:20 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-21 12:22 [Bug bootstrap/98412] New: " ebotcazou at gcc dot gnu.org 2020-12-21 12:26 ` [Bug bootstrap/98412] " jakub at gcc dot gnu.org 2020-12-21 13:42 ` nathan at gcc dot gnu.org 2020-12-21 16:04 ` ebotcazou at gcc dot gnu.org 2020-12-21 16:06 ` ebotcazou at gcc dot gnu.org 2020-12-21 16:43 ` nathan at gcc dot gnu.org 2020-12-21 17:11 ` ebotcazou at gcc dot gnu.org 2020-12-21 17:20 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-21 17:42 ` nathan at gcc dot gnu.org 2020-12-22 6:58 ` nikhil.benesch at gmail dot com 2020-12-22 12:45 ` nathan 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-98412-4-4N6u3DbTzR@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).