public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/26848] Build failure due to missing previous declaration Date: Tue, 10 Nov 2020 20:13:18 +0000 [thread overview] Message-ID: <bug-26848-4717-RTlPdp4Ab1@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26848-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26848 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c51cf513d98adcf34a342c7e9d885a6c788cda8 commit 6c51cf513d98adcf34a342c7e9d885a6c788cda8 Author: Tom Tromey <tromey@adacore.com> Date: Mon Nov 9 06:55:39 2020 -0700 Move include block to pathstuff.h A recent commit caused pathstuff.cc to fail to compile on mingw, like: ../../binutils-gdb/gdbsupport/pathstuff.cc:324:1: error: no previous declaration for 'std::string find_gdb_home_config_file(const char*, _stati64*)' [-Werror=missing-declarations] Some newly-added #includes were changing which "stat" was being seen by the compiler. This patch moves the includes to the header, so that the declaration and definition now agree. 2020-11-10 Tom Tromey <tromey@adacore.com> PR build/26848: * pathstuff.h: Move include block here... * pathstuff.cc: ... from here. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-10 20:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-05 23:17 [Bug build/26848] New: " markus.boeck02 at gmail dot com 2020-11-06 1:04 ` [Bug build/26848] " simark at simark dot ca 2020-11-10 20:12 ` tromey at sourceware dot org 2020-11-10 20:13 ` cvs-commit at gcc dot gnu.org [this message] 2020-11-10 20:14 ` tromey at sourceware dot 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-26848-4717-RTlPdp4Ab1@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).