[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Terrible problem with latest CVS libtool
From: |
Bob Friesenhahn |
Subject: |
Re: Terrible problem with latest CVS libtool |
Date: |
Sun, 30 Nov 2003 17:32:52 -0600 (CST) |
> > + 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 being expanded in a the wrong
order for some reason. I have tried using bash and GNU sed, but the
problem still continues. Playing on the shell command line seems to
produce the same bad result. This is also true for Solaris where
config.status seems to behave.
Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen