Hi Kevin,
Thanks for the analysis.
I think we need to take a careful look at the (complicated) echo testing in
libtool.m4 and figure out how this behaviour is not noticed by the current
tests.
I won't have time to do this myself until later in the Summer (in time for
libtool-1.5), so if you
I think I was getting a bit off track before. Some cut down bad
behaviour can be seen, I think, from a file "foo" containing the
following
blah blah \\\` blah blah
and run a script
if test -n "$ZSH_VERSION"; then emulate sh; fi
eval "bar=\\\"\`cat foo\`\\\""
cat < \ gets done. Don't know if t
"Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
>
> Oh dear. I thought zsh was sane enough to do the right thing when
> argv[0] == /bin/sh =(O| I take it that it is zsh builtin echo that
> is the culprit here. Does /bin/echo work correctly?
No, gives the same. And my own program doing a printf i
On Monday 16 April 2001 11:56 pm, Kevin Ryde wrote:
> I wrote:
> > so maybe it's sed.
>
> Or maybe not.
>
> eval "bar=\\\"\` echo \"\$quote\" \`\\\""
> echo $bar
>
> in bash gives what I assume is the expected result
>
> "s/\([\\"\\`$]\)/\\\1/g"
>
> whereas on Darwin
>
> "s/\([
I wrote:
> so maybe it's sed.
Or maybe not.
eval "bar=\\\"\` echo \"\$quote\" \`\\\""
echo $bar
in bash gives what I assume is the expected result
"s/\([\\"\\`$]\)/\\\1/g"
whereas on Darwin
"s/\([\\"\\`$]\)/\1/g"
Actually Darwin /bin/sh looks like it's zsh (should ha
"Gary V. Vaughan" <[EMAIL PROTECTED]> writes:
>
> It looks like the echo command found by libtool is removing some of the
> backslashes that it is supposed to leave behind.
Yep.
> And this is what I get:
>
> $ echo $bar
> "\\\`"
Yep, on i386 debian or freebsd.
> I guess you will get:
>
Hi Kevin,
It looks like the echo command found by libtool is removing some of the
backslashes that it is supposed to leave behind. Here is what it boils down
to:
$ echo=echo
$ foo='`'
$ quote='s/\([\\"\\`$]\)/\\\1/g'
$ double_quote='s/\([\\"\\`]\)/\\\1/g'
$ delay='s/
On Apr 13, 2001, Christoph Pfisterer <[EMAIL PROTECTED]> wrote:
> I think the issue here is the quoting of the backticks. The patch I
> originally submitted used $( ... ) instead of ` ... ` to avoid
> problems...
The problem is that $( ) isn't portable.
--
Alexandre Oliva Enjoy Guarana', see
Kevin Ryde wrote:
>On Darwin 1.3 with libtool 1.3d or the current cvs, the quoting of
>archive_cmds provokes a warning about an unmatched ". It comes
>through to the generated libtool script as the following long line,
>
>archive_cmds="\$CC \\`test .\$module = .yes && echo -bundle || echo
>-dyna
On Darwin 1.3 with libtool 1.3d or the current cvs, the quoting of
archive_cmds provokes a warning about an unmatched ". It comes
through to the generated libtool script as the following long line,
archive_cmds="\$CC \\`test .\$module = .yes && echo -bundle || echo -dynamiclib\\`
\$allow_undefi
10 matches
Mail list logo
