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 att
Got your attention?
Let me show you the way Financial Independence: www.saax.org?axel=49
No more advertisements, thanks - www.5jzd.org/out5s/pre-rem2e.asp
cswuzwsn
bgcc ngjrdio
cyed pgdms r
el tqn wfyrhwnx
jukvwgf ujn ytqui iy
_
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.s
'make distclean' does not work for libtool, and has not worked for a
long time due to the effect of the tests subdirectories. While 'make
clean' sometimes appears to work, it does not fully clean the tests
directories. This means that
make distclean
./configure
make clean
make
make chec
Regarding the missing SED bug, I believe that the bug is in the
config.status section which produces quoted lt_foo variables. I
suspect this because $SED is properly set to /bin/sh before this
point, yet $lt_SED is set to nothing.
Error messages are emitted from line 527 of config.status:
eval
Here is some relevant config.status debug output:
+ SED=/bin/sed
+ Xsed=sed -e s/^X//
.
.
.
+ eval lt_SED=\`$echo X$SED
+ X/bin/sed
+ lt_SED=`print -r
config.status[527]: X/bin/sed: not found
+ $Xsed -e $sed_quote_subst`\
config.status[527]: $Xsed: not found
+ eval lt_SHELL=\`$echo X$SHELL
+ X/b
On Sun, Nov 30, 2003 at 04:12:55PM -0600, Bob Friesenhahn wrote:
> Here is some relevant config.status debug output:
>
> + SED=/bin/sed
> + Xsed=sed -e s/^X//
> .
> .
> .
> + eval lt_SED=\`$echo X$SED
> + X/bin/sed
> + lt_SED=`print -r
> config.status[527]: X/bin/sed: not found
Looks like $echo
> > + eval lt_SED=\`$echo X$SED
> > + X/bin/sed
> > + lt_SED=`print -r
> > config.status[527]: X/bin/sed: not found
>
> Looks like $echo is NULL.
Not so:
+ echo=print -r
That is where the 'print -r' comes from at the front of the lt_SED
assignment.
My best guess is that the expression is bein
