public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/101834] make distclean forgets ./c++tools/
Date: Thu, 30 Mar 2023 11:53:33 +0000	[thread overview]
Message-ID: <bug-101834-4-rC1TkY8TDK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101834-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101834

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This seems like an improvement ...


--- a/c++tools/Makefile.in
+++ b/c++tools/Makefile.in
@@ -22,6 +22,7 @@ libexecdir := @libexecdir@
 target_noncanonical := @target_noncanonical@
 gcc_version := $(shell @get_gcc_base_ver@ $(srcdir)/../gcc/BASE-VER)
 libexecsubdir := $(libexecdir)/gcc/$(target_noncanonical)/$(gcc_version)
+INSTALL := @INSTALL@
 INSTALL_PROGRAM := @INSTALL_PROGRAM@
 INSTALL_STRIP_PROGRAM := $(srcdir)/../install-sh -c -s
 AUTOCONF := @AUTOCONF@
@@ -41,13 +42,14 @@ all::
 mostlyclean::
        rm -f $(MAPPER.O)

-clean::
+clean:: mostlyclean
        rm -f g++-mapper-server$(exeext)

-distclean::
-       rm -f config.log config.status config.h
+distclean:: clean
+       rm -f config.log config.status config.h config.cache Makefile
+       rm -f $(MAPPER.O:%.o=%.d)

-maintainer-clean::
+maintainer-clean:: distclean

 install::

@@ -132,6 +134,6 @@ config.h: config.status config.h.in
 config.status: $(srcdir)/configure $(srcdir)/config.h.in
        if test -x $@; then ./$@ -recheck; else $< @configure_args@; fi

-.PHONY: all check clean distclean maintainer-clean
+.PHONY: all check mostlyclean clean distclean maintainer-clean

 -include $(MAPPER.O:.o=.d)

  parent reply	other threads:[~2023-03-30 11:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 18:42 [Bug other/101834] New: " dilyan.palauzov at aegee dot org
2021-08-09 18:47 ` [Bug bootstrap/101834] " pinskia at gcc dot gnu.org
2022-12-14 16:40 ` pinskia at gcc dot gnu.org
2022-12-14 17:28 ` segher at gcc dot gnu.org
2023-03-30 10:59 ` segher at gcc dot gnu.org
2023-03-30 11:24 ` redi at gcc dot gnu.org
2023-03-30 11:37 ` redi at gcc dot gnu.org
2023-03-30 11:45 ` segher at gcc dot gnu.org
2023-03-30 11:46 ` segher at gcc dot gnu.org
2023-03-30 11:48 ` segher at gcc dot gnu.org
2023-03-30 11:53 ` redi at gcc dot gnu.org [this message]
2023-03-30 12:00 ` redi at gcc dot gnu.org
2023-03-30 12:16 ` redi at gcc dot gnu.org
2023-03-31  9:39 ` cvs-commit at gcc dot gnu.org
2023-03-31  9:40 ` redi 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-101834-4-rC1TkY8TDK@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).