aboutsummaryrefslogtreecommitdiff
path: root/ct-ng.in
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2011-03-20 00:02:21 +0100
committerYann E. MORIN" <yann.morin.1998@anciens.enib.fr>2011-03-20 00:02:21 +0100
commit7bfa4139adfb9175ade8787a425a3baedee7a748 (patch)
treecd9235736a2755658e7706a16aed7de89820f52b /ct-ng.in
parenta5d9facb144a937e56b484fb8f23ec68ada94598 (diff)
downloadcrosstool-ng-7bfa4139adfb9175ade8787a425a3baedee7a748.tar.gz
crosstool-ng-7bfa4139adfb9175ade8787a425a3baedee7a748.tar.bz2
crosstool-ng-7bfa4139adfb9175ade8787a425a3baedee7a748.zip
scripts: leave changelog in build dir, copy to install dir
Users tend to look for the build log in the current working directory, rather than in the toolchain's installation dir. While bundling the build log in the toolchain installation dir is nice for distribution and review, it can be easier to have the build log readily available in the working directory, as it is quicker to get to it. So, the build log stays in the working directory until the toolchain is completely and successfully built, and then a (compressed) copy is made. Reported-by: Trevor Woerner <twoerner@gmail.com> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Diffstat (limited to 'ct-ng.in')
-rw-r--r--ct-ng.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/ct-ng.in b/ct-ng.in
index 699d0456..0233622d 100644
--- a/ct-ng.in
+++ b/ct-ng.in
@@ -165,7 +165,7 @@ version:
PHONY += clean
clean::
@$(ECHO) " CLEAN log"
- $(SILENT)rm -f log.* .config.* ..config*
+ $(SILENT)rm -f build.log .config.* ..config*
PHONY += distclean
distclean:: clean