[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs build prob

From: Gary V. Vaughan
Subject: Re: cvs build prob
Date: Thu, 29 Jul 2004 19:48:58 +0100
User-agent: Mozilla Thunderbird 0.7 (X11/20040615)

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 output_verbose_link_cmd?
> That's it - I first just tried installing a new cvs-autoconf with Paul's
> patch. That didn't fix the LT_LANG(C++) using quoting problem. I then
> got rid of the backslashes as per your patch, and that made libtool.m4
> happy.

That's bad :-(

I've only been able to remove the bogus nested escaped double quotes in
some of libtool.m4, including the one that triggers with your particular
combination of host, compiler and shell.  If the AS_SHELL_SANITIZE isn't
placating pdksh, then other combinations of host/compiler/shell will
still trip over the quotes I couldn't strip.

The key is in this part of the manual page:

  echo "`echo \"hi\"`" produces `"hi"' in posix mode, `hi' in non-posix mode

Let's see what bash does:

bash$ echo "`echo \"hi\"`"
bash$ set -o posix
bash$ echo "`echo \"hi\"`"

And now pdksh:

ksh$ echo "`echo \"hi\"`"
ksh$ set -o posix
ksh$ echo "`echo \"hi\"`"
ksh$ set +o posix
ksh$ echo "`echo \"hi\"`"

So, it appears that pdksh is confused over what the posix behaviour should
be :-(

I think autoconf should test for that bug and skip a shell that has it when
searching for a suitable shell...


Gary V. Vaughan      ())_.  address@hidden,}
Research Scientist   ( '/
GNU Hacker           / )=
Technical Author   `(_~)_

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]