Akim> 1. we add diversions which makes it possible to specify some
Akim>    processing of the options, and we don't support --target etc. by
Akim>    default.

Akim> 2. when AC_CAN_TARGET is called, a variable is set very high in
Akim>    configure which tells the options handling machinery that --target
Akim>    is enabled.

And would it be an error if --target is given to a configure script
which doesn't claim to support it?  Or would --target just not appear
in --help output?

If the former, then I'm against it.  Consider making a Cygnus-style
tree.  What you're saying is that anybody who does this (not just
Cygnus, the gcc and gdb net repositories do this too) has to maintain
local modifications to the configure.in for each package they import.
This is lame.

Tom

Reply via email to