Akim Demaille <[EMAIL PROTECTED]> wrote:
| | It looks like it'll work just fine as long as you don't
| | put quotes around `bison -y'.
| |
| | $ printf '%%%%\na:\n%%%%\n' > j.y
| | $ sh missing --run bison -y j.y
| | $
| |
|
| Yes, that's not what I meant. My question is that ISTR that Automake
| supports `missing'ing yacc, and we must make sure that in this case
| `bison -y' is properly passed as two entities.
I wouldn't worry about it.
There's no need to put quotes around `bison -y' in a make variable.
My point is that with the suggested change, `missing' will work the
same way the existing code does.
| | | Still, I wonder to what extend what you found means we should change
| | | all the place where we invoke `"$@"' as command line. The only
| | | restriction is wrt $1 being `:'?
| |
| | Hmm... at first I thought it was independent of the actual value,
| | but just tested it and see that it may indeed be specific to `:':
| |
| | $ p=:
| | $ "$p"
| | º: not found
| | $ p=echo
| | $ "$p"
| |
| | $
|
| Aha! It is the 8th bit problem again. Then try this:
|
| p=":"
| "$p"
Still fails:
$ p=":"
$ "$p"
º: not found
$
| maybe it will work. No guarantee, but as shocking as it may seem, I
| wouldn't be surprised that it works.
|
| The difference might be that with `echo' it had to look in PATH, if
| it's not a build in. Then, we can imagine plenty of places where the
| 8th big is reversed again. Give a try to `cd' as it must be a
| builtin.
$ "cd"
ãä: not found
$
| In fact, does
|
| ":"
|
| alone, work?
$ ":"
º: not found
$
