Patrick,
Yes something is wrong here, I'm currently working on fixing this
but I didn't know it was broken in CVS Libtool. The problem I'm
having is that $SED needs to be set earlier than it currently is,
so the resulting libtool is attempting to operate with untested
"sed" which fails (a lot!) when doing piecewise linking of large
libraries. Anyway, I'm looking into this so it should be fixed
soon.
Robert
-----Original Message-----
From: Patrick Welche [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 13, 2002 12:02 PM
To: [EMAIL PROTECTED]
Subject: SED ?
Using cvs libtool from just now, which passed everything :-), I tried
bootstraping sasl, and found that the libtool generated died at
progname=`$echo "$0" | ${SED} 's%^.*/%%'`
modename="$progname"
because SED was empty - where should SED be defined? (Adding SED=sed just
before the above had it working, but something must wrong in there..)
Cheers,
Patrick
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
