Re: cvs build prob

[Gary V. Vaughan]

Hi Patrick!

Patrick Welche wrote:
> On Tue, Jul 27, 2004 at 01:25:43PM -0700, Paul Eggert wrote:
> 
>>"Gary V. Vaughan" <address@hidden> writes:
>>The workaround in this case is easy.  Just omit the outer quotes and
>>remove the inner backslashes:
>>
>>output_verbose_link_cmd=`$echo "X$output_verbose_link_cmd" | $Xsed -e 
>>"$no_glob_subst"`
>>
>>The outer quotes aren't needed.  This issue is discussed in the
>>Autoconf manual's Shellology section.
> 
> 
> I'm now quite confused :-) I can verify that Gary's libtool patch, which
> does the above, fixes things, but I find I need the opposite as an
> autoconf patch (attached).

I guess you're talking about libtool--devo--1.0--patch-92, right?

It is very "belt and braces".  Not only have I fixed the obvious cases
of nested escaped double quotes in libtool.m4, but I've added the new
KSH_VERSION toting AS_SHELL_SANITIZE expansion to ltmain.in (and hence
the generated libtool script) and libtoolize.in.  There are other nested
escaped double quotes in libtool.m4 that I can't remove simply though,
hence the note about bootstrapping with CVS autoconf...

The quote removal you reference above is probably what fixes your
immediate problem, but I guess the new AS_SHELL_SANITIZE is triggering
something else. :-(

If you revert my patch, or fetch the prepatch revision from my arch
mirror, and bootstrap with HEAD autoconf, does the new AS_SHELL_SANITIZE
from autoconf prevent the crash when setting output_verbose_link_cmd?

Cheers,
        Gary.
-- 
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature