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 archite
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 @(#)PD KSH v5.2.14 99/07/13.2)
.. and it is explained in TFM:
The following is a list of things that are affected by the state of the
posix opt
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 @
On Tue, Jul 27, 2004 at 05:15:17PM +0100, Patrick Welche wrote:
> Reminder of the miscreant line:
>
> output_verbose_link_cmd="`$echo \"X$output_verbose_link_cmd\" | $Xsed -e
> \"$no_glob_subst\"`"
>
Why not replacing it with
output_verbose_link_cmd=`$echo "X$output_verbose_link_cmd" | $Xsed
On Tue, Jul 27, 2004 at 11:23:29AM -0500, Bob Friesenhahn wrote:
> There must be a syntax which works in all cases. We have encountered
> (and fixed) this backslash problem before.
Just removing the extra backslashs in that line "work for me", but I don't
know if that will work always..
Cheers,
Alexandre Duret-Lutz wrote:
> On Tue, Jul 27, 2004 at 05:15:17PM +0100, Patrick Welche wrote:
>
>>Reminder of the miscreant line:
>>
>> output_verbose_link_cmd="`$echo \"X$output_verbose_link_cmd\" | $Xsed -e
>> \"$no_glob_subst\"`"
>>
>
>
> Why not replacing it with
>
> output_verbose_link_c
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
"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:
>>
>> output_ver
