[pkgsrc/trunk]: pkgsrc/mk/configure Add missing "rm" statement that was causi...

[jlam <jlam%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/71a35d60acdc
branches:  trunk
changeset: 515740:71a35d60acdc
user:      jlam <jlam%pkgsrc.org@localhost>
date:      Fri Jul 07 14:06:57 2006 +0000

description:
Add missing "rm" statement that was causing the libtool wrapper to be
overwritten in the case where LTCONFIG_OVERRIDE was defined.

As a side note, after analyzing the way that the original code in
bsd.pkg.mk worked, I think we can nuke LTCONFIG_OVERRIDE completely,
but we'll need a bulk build to verify this.  The original code always
replaced the libtool scripts because LIBTOOL_OVERRIDE is always defined
in bsd.pkg.use.mk, so LTCONFIG_OVERRIDE essentially had no effect.

diffstat:

 mk/configure/libtool-override.mk |  3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diffs (17 lines):

diff -r 0a19eb166366 -r 71a35d60acdc mk/configure/libtool-override.mk
--- a/mk/configure/libtool-override.mk  Fri Jul 07 13:39:52 2006 +0000
+++ b/mk/configure/libtool-override.mk  Fri Jul 07 14:06:57 2006 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: libtool-override.mk,v 1.1 2006/07/05 06:09:15 jlam Exp $
+# $NetBSD: libtool-override.mk,v 1.2 2006/07/07 14:06:57 jlam Exp $
 
 ######################################################################
 ### {ltconfig,libtool,shlibtool}-override (PRIVATE)
@@ -53,6 +53,7 @@
 
 .for _script_ in libtool shlibtool
 _SCRIPT.${_script_}-override=                                          \
+       ${RM} -f $$file;                                                \
        ${ECHO} "\#!"${TOOLS_SH:Q} > $$file;                            \
        ${ECHO} "exec" ${_OVERRIDE_PATH.${_script_}:Q} '"$$@"' >> $$file; \
        ${CHMOD} +x $$file