I still have not figured out what the cause of the config.status/libtool SED problem is, but I have determined that it is platform dependent. The problem does not occur under Solaris & FreeBSD, but it does occur under IRIX and AIX.
I am using Autoconf 2.58 and Automake 1.7.9. The problem config.status includes # A sed program that does not truncate output. SED=$lt_SED The problem libtool includes # A sed program that does not truncate output. SED= A good config.status also includes # A sed program that does not truncate output. SED=$lt_SED But a good libtool defines the value of SED determined by the configure script: # A sed program that does not truncate output. SED="/bin/sed" Bob On Sun, 30 Nov 2003, Bob Friesenhahn wrote: > The generated config.status script includes: > > # A sed program that does not truncate output. > SED=$lt_SED > > # Sed that helps us avoid accidentally triggering echo(1) options like -n. > Xsed="$SED -e s/^X//" > > On at least IRIX and AIX (all I have tested thus far) lt_SED is never > set. This results in attempts to run the X11 server on both operating > systems. When libtool is used, there are attempts to execute the sed > expressions. I expect that this bug appears whenever GNU sed is not > present. GNU sed should not be required in order to configure and > build a package. > > Naturally, GNU libtool developers always have GNU sed handy so this > problem is not noticed. > > Bob > ====================================== > Bob Friesenhahn > [EMAIL PROTECTED] > http://www.simplesystems.org/users/bfriesen > > > > _______________________________________________ > Libtool mailing list > [EMAIL PROTECTED] > http://mail.gnu.org/mailman/listinfo/libtool > ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen _______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/libtool
