| On Oct 25, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
| >>>>>> "Daniele" == Daniele Arena <[EMAIL PROTECTED]> writes:
| Daniele> This one seemed to be working better... At least it gave no
| Daniele> errors on exit and it did create a Makefile. Hope it's fixed?
|
| > OK, then the problem is that your shell is bad at following escaped
| > quotes.
|
| > ac_file_inputs=`IFS=:
| [snip]
| > test -f "$f" || { echo "configure: error: cannot find input file \\\`$f'"
|>&2; exit 1; }
|
| I don't think a shell is required to do it. Remember the problem I
| had told you about:
|
| foo="`something with a "quote" mark`"
| in which ^ this would match ^ this?
Yeah, I know this guy! Andreas Schwab sent a huge patch IIRC :)
| This is just another instance of the same problem, with a different
| quote mark.
Agreed. Nevertheless this is the first shell that triggers the
problem, while it's been in Autoconf since quite a while now.
| Maybe we should set ac_backquote and ac_singlequote upfront, and use
| it in error messages instead?
Why not. That's hacky, but that's a way out :)
| > Maybe we should go to using `read'
|
| What do you mean? In what sense would this help?
I meant still keeping a for-echo loop, but using `read' outside.
| > Is xargs portable?
|
| Nope.
:(
