From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 9159A3856DE2; Sun, 31 Jul 2022 10:33:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9159A3856DE2
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106429] make clean in libgcc fails
Date: Sun, 31 Jul 2022 10:33:03 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 11.2.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-106429-4-sEXwvt9Jv2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106429-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106429-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jul 2022 10:33:03 -0000

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

--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Martin Vahi from comment #11)
> For me the "make clean" is a standard feature that is like the close butt=
on
> at the corner of a window. For me, the fact that someone does not bother =
to
> use the close button at the corner of the window is not an excuse, why the
> button at the corner of the window should not work as expected. The same
> with the "make clean": it is nice to do it automatically just to make sure
> that I won't waste my human-life-minutes/hours on some triviality that co=
mes
> from leaving old build results laying around.=20

So delete the whole build tree. Why would you want to keep an empty directo=
ry
around after running 'make clean'?


>=20
> Actually, with some projects, I do not remember, which, there was a
> distinction between "make clean" and "make clear", where the "make clear"
> reset the source tree to the state as it is expected to be after fresh
> checkout and the "make clean" was allowed to not delete all build system
> generated files.

The GCC build should be done outside the source tree, and won't change anyt=
hing
in the source tree anyway, so that distinction would be pointless. The sour=
ce
tree is left clean, and the build tree can be removed after building.

I agree it shouldn't crash, but it also doesn't need to be used at all. It's
there because automake always adds a 'clean' target to makefiles, not becau=
se
it's useful.=