remove this#
> # macro and use it instead. #
> ####
> -# LT_AC_PROG_SED
> -# --
> -# Check for a fully-functional sed program, that truncates
> -# as few characters as possib
HEAD to fix this.
>
>> 4) In CVS libtool, we don't provide backward compatibility for
>> LT_AC_PROG_SED. We probably should.
>
> I think it would be safe to ignore this: we never advertised
> LT_AC_PROG_SED. Users would be best to not use it. People needing it
> would
9) to
> always pull in this libtool.m4. Even if the user does not use
> AC_PROG_LIBTOOL at all, as in:
> AC_INIT
> AC_PROG_SED
> AC_OUTPUT
I have applied the patch below to HEAD to fix this.
> 4) In CVS libtool, we don't provide backward compatibility for
>LT_A
A quick summary:
* Thomas Porschberg wrote on Wed, Jan 18, 2006 at 02:05:23PM CET:
> > * Thomas Porschberg wrote on Tue, Jan 17, 2006 at 08:27:45AM CET:
> > >
> > > I meet a problem with a configure.ac script which does call
> > > LT_AC_PROG_SED. However SE
On Wed, Jan 18, 2006 at 01:20:29PM +0100, Ralf Wildenhues wrote:
> Hi Thomas,
>
> Thanks, several bugs for the price of one bug report.
>
> * Thomas Porschberg wrote on Tue, Jan 17, 2006 at 08:27:45AM CET:
> >
> > I meet a problem with a configure.ac script which
&
Hi Thomas,
Thanks, several bugs for the price of one bug report.
* Thomas Porschberg wrote on Tue, Jan 17, 2006 at 08:27:45AM CET:
>
> I meet a problem with a configure.ac script which
> does call LT_AC_PROG_SED.
> However SED is not substituted with the sed command
> and the c
Hi,
I meet a problem with a configure.ac script which
does call LT_AC_PROG_SED.
However SED is not substituted with the sed command
and the configure failed.
I hardcoded SED=sed as a workaround and it worked.
Does the call of LT_AC_PROG_SED has any preconditions,
what must I call before
