Front page | perl.perl5.porters |
Postings from July 2013
On Mon, Jul 29, 2013 at 04:13:49PM -0700, "James E Keenan via RT" wrote:
> Fergal, Nicholas: Please review the patch to INSTALL attached.
Thank you for following up on this old ticket.
I have applied the following patch to INSTALL to document what the
make clean target actually does. Whether or not that's useful depends
on what the user is trying to do. This does not solve the original
poster's problem that 'make clean' might attempt to build perl as part
of the cleanup process, but I don't see anyway to solve that problem.
('make realclean' suffers from the same problem, so my comment earlier
on this ticket about clean vs. realclean was not relevant.)
commit c23a69e83f410b43450b9f1e9696d04795aae758
Author: Andy Dougherty <doughera@lafayette.edu>
Date: Tue Jul 30 10:57:32 2013 -0400
Mention the 'make clean' makefile target [perl #38307].
Mention the 'make clean' target in INSTALL. It cleans up a lot,
but not everything. Since perl is used extensively in its own
build process, it may involve attempting to build perl in order
to clean up. Alternatively, we could just make 'clean' an
alias for 'realclean'.
diff --git a/INSTALL b/INSTALL
index c4d2247..4a141eb 100644
--- a/INSTALL
+++ b/INSTALL
@@ -2271,7 +2271,9 @@ or
make realclean
The only difference between the two is that make distclean also removes
-your old config.sh and Policy.sh files.
+your old config.sh and Policy.sh files. (A plain 'make clean' will not
+delete the makefiles used for rebuilding perl, and will also not delete
+a number of library and utility files extracted during the build process.)
If you are upgrading from a previous version of perl, or if you
change systems or compilers or make other significant changes, or if
--
Andy Dougherty doughera@lafayette.edu
Dept. of Physics
Lafayette College, Easton PA 18042
Thread Previous
|
Thread Next