While working on some other stuff, I noticed that tests/sh.test is
calling $SED without it being set, though this was only causing a
warning message and the test passed.  I'm not sure this was the best way
to handle it (perhaps configure should look for sed?), but I fixed the
warning by having $SED default to `sed' in the attached patch.

2005-07-07  Derek R. Price  <[EMAIL PROTECTED]>

    * tests/sh.test (SED): Default variable contents to `sed'.


Cheers,

Derek



_______________________________________________
Bug-libtool mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-libtool

Reply via email to