SED and old ltconfig files

[Jens Petersen]

Hello,

This problem has come before in the mailing lists I think,
but I haven't seen any solution proposed yet.

The introduction of SED in ltmain.sh in 1.4.3 creates
problems when running libtoolize in projects with a ltconfig
created by Libtool 1.3.  Basically the problem is that it
creates a libtool script in the project which doesn't define
SED, and then things go wrong.  I think this problem is
probably a barrier to the adoption of 1.4.3.  The patch
below works around the problem by defining SED in ltmain.sh
before it is used if it isn't set.  Perhaps there is a more
elegant solution, but this seems to work better at least.

Jens


--- libtool-1.4.3/ltmain.sh~    2002-10-23 11:26:24.000000000 +0900
+++ libtool-1.4.3/ltmain.sh     2002-11-23 11:56:58.000000000 +0900
@@ -48,6 +48,9 @@
   exit 0
 fi
 
+# define SED for historic ltconfig's generated by Libtool 1.3
+SED=${SED:-sed}
+
 # The name of this program.
 progname=`$echo "$0" | ${SED} 's%^.*/%%'`
 modename="$progname"