[autoconf-conversion] New tools and multilibs fight with one another
Ian Lance Taylor
ian at airs.com
Fri Jul 25 19:13:06 UTC 2003
Phil Edwards <phil at jaj.com> writes:
> So, when a target library's configure "source"s the toplevel config-ml.in,
> and config-ml.in looks at the command-line args, all the env variables
> passed down from the toplevel are also visible in the argument list.
>
> Somewhere, some quoting gets lost.
My guess is that the quoting is lost here:
ml_arguments="${ac_configure_args}"
...
for option in ${ml_arguments}
I see no real need for the ml_arguments variable. Try simply
replacing all uses of ml_arguments with ac_configure_args in
config-ml.in.
Ian
More information about the autoconf-conversion
mailing list