public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/9346: make uninstall does not remove all files
Date: Fri, 17 Jan 2003 11:16:00 -0000 [thread overview]
Message-ID: <20030117111603.25787.qmail@sources.redhat.com> (raw)
The following reply was made to PR other/9346; it has been noted by GNATS.
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <drepper@redhat.com>
Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>
Subject: Re: other/9346: make uninstall does not remove all files
Date: Fri, 17 Jan 2003 11:10:41 +0000 (GMT)
On 17 Jan 2003 drepper@redhat.com wrote:
> After running 'make install' the use of 'make uninstall' does not
> remove all the files. In the $prefix/bin directly the following files
> are left:
"make uninstall" is documented (in the install manual) to be unsupported.
We should, however, either support it properly (removing that
documentation and the corresponding statement in sourcebuild.texi that
front ends need not do anything in their <lang>.uninstall hooks, and
documenting the target for users), as a target in the GNU Coding
Standards, or unsupport it properly and remove the bitrotten rules and
deliberately not support this part of the GNU Coding Standards (as with
"make dist").
So either way there is a bug here: the presence of bitrotten "uninstall"
rules.
--
Joseph S. Myers
jsm28@cam.ac.uk
next reply other threads:[~2003-01-17 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 11:16 Joseph S. Myers [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-17 4:56 drepper
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=20030117111603.25787.qmail@sources.redhat.com \
--to=jsm28@cam.ac.uk \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).