Re: Darwin and archive_cmds quoting

[Kevin Ryde]

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 <<EOF
bar is: $bar
EOF

in ash or bash this gives

        bar is: "blah blah \\\` blah blah"

whereas in zsh it gives

        bar is: "blah blah \\` blah blah"

And I think this is the source of the wrong backslashes in the
generated libtool archive_cmds.

If more backslashes are added to the input file, it looks like a
transform \\ -> \ gets done.  Don't know if that's right or wrong, but
it might at least give something that could be tested for.