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/12440] `make distclean' failing - with patch Date: Tue, 01 Mar 2022 23:54:28 +0000 [thread overview] Message-ID: <bug-12440-4717-mH4q2UVl4u@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12440-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=12440 --- Comment #6 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=c675db743ec2634f1f5f185fa8a6e73eb59447f7 commit c675db743ec2634f1f5f185fa8a6e73eb59447f7 Author: Tom Tromey <tom@tromey.com> Date: Sun Feb 27 17:31:54 2022 -0700 Some "distclean" fixes in gdb PR build/12440 points out that "make distclean" is broken in gdb. Most of the breakage comes from other projects in the tree, but we can fix some of the issues, which is what this patch does. Note that the yacc output files, like c-exp.c, are left alone. In a source distribution, these are included in the tarball, and if the user builds in-tree, we would not want to remove them. While that seems a bit obscure, it seems to me that "distclean" is only really useful for in-tree builds anyway -- out-of-tree I simply delete the entire build directory and start over. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=12440 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-01 23:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-26 0:10 [Bug build/12440] New: " fmn at oneiroi dot net 2011-01-26 0:14 ` [Bug build/12440] " fmn at oneiroi dot net 2022-02-27 23:39 ` tromey at sourceware dot org 2022-02-27 23:50 ` tromey at sourceware dot org 2022-02-28 0:27 ` tromey at sourceware dot org 2022-02-28 0:34 ` tromey at sourceware dot org 2022-03-01 23:54 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-01 23:55 ` 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-12440-4717-mH4q2UVl4u@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).