Re: cvs build prob

2004-07-29 Thread Patrick Welche
On Wed, Jul 28, 2004 at 06:38:56PM +0100, Gary V. Vaughan wrote: 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? That's it - I

Re: cvs build prob

2004-07-29 Thread Gary V. Vaughan
Patrick Welche wrote: On Wed, Jul 28, 2004 at 06:38:56PM +0100, Gary V. Vaughan wrote: 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

Re: cvs build prob

2004-07-28 Thread Patrick Welche
On Tue, Jul 27, 2004 at 01:25:43PM -0700, Paul Eggert wrote: Gary V. Vaughan [EMAIL PROTECTED] 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`

Re: cvs build prob

2004-07-27 Thread Patrick Welche
I can reproduce the sed: 1: s/\*/\\\*/g: invalid command code error with the minimum configure.ac which contains LT_LANG(C++) which calls _LT_LANG_CXX_CONFIG, which calls AC_LIBTOOL_PROG_LD_SHLIBS, which calls AC_LIBTOOL_POSTDEP_PREDEP, which has # The `*' in the case matches for

Re: cvs build prob

2004-07-27 Thread Bob Friesenhahn
There must be a syntax which works in all cases. We have encountered (and fixed) this backslash problem before. Bob On Tue, 27 Jul 2004, Patrick Welche wrote: On Tue, Jul 27, 2004 at 04:07:14PM +0100, Patrick Welche wrote: The great part is this is a ksh quoting problem: Oh joy... (ksh version

Re: cvs build prob

2004-07-27 Thread Gary V. Vaughan
Hi Patrick, Good catch! I'm CCing the autoconf list, as this is probably a candidate for AS_SHELL_SANITIZE, and the comparative shellology documentation... Patrick Welche wrote: On Tue, Jul 27, 2004 at 04:07:14PM +0100, Patrick Welche wrote: The great part is this is a ksh quoting problem:

Re: cvs build prob

2004-07-27 Thread Paul Eggert
Gary V. Vaughan [EMAIL PROTECTED] writes: Good catch! I'm CCing the autoconf list, as this is probably a candidate for AS_SHELL_SANITIZE, and the comparative shellology documentation... Thanks. I installed the patch enclosed below. Reminder of the miscreant line:

cvs build prob

2004-07-26 Thread Patrick Welche
I get: libtool: Version mismatch error. This is libtool 1.5b, revision AR=ar AR_FLAGS... libtool: but the definition used by this AC_PROG_LIBTOOL comes from revision libtool: 1.1527. libtool: You should recreate aclocal.m4 with macros from revision AR=ar AR_FLAGS... libtool: of libtool 1.5b and

Re: cvs build prob

2004-07-26 Thread Bob Friesenhahn
I saw a problem similar to this but resolved it by moving the installed libtool.m4 to the side, running aclocal, and re-running the libtool bootstrap script. After that I hit the VPATH problems mentioned earlier on the libtool-patches list and am dead in the water. :-) Bob On Mon, 26 Jul