>>>>> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> Yes, but what I am asking for is to actually set the prefix and
Mo> exec_prefix variables after reading the command line options in
Mo> ./configure, and then pass them correctly to ./config.status.
I answered to this elsewhere: there are some case where you want to
know if the user has set prefix or it.
But I agree it would be much more pleasant to have a variable stating
explicitly that ac_prefix_user_set etc.
Still, maybe we can even avoid this if we get rid of some macros
(which, IMHO, are doing wrong wrt to the expected semantics of a
./configure): AC_PREFIX_DEFAULT and AC_PREFIX_PROGRAM.
Default Prefix
==============
By default, `configure' sets the prefix for files it installs to
`/usr/local'. The user of `configure' can select a different prefix
using the `--prefix' and `--exec-prefix' options. There are two ways
to change the default: when creating `configure', and when running it.
Some software packages might want to install in a directory besides
`/usr/local' by default. To accomplish that, use the
`AC_PREFIX_DEFAULT' macro.
- Macro: AC_PREFIX_DEFAULT (PREFIX)
Set the default installation prefix to PREFIX instead of
`/usr/local'.
It may be convenient for users to have `configure' guess the
installation prefix from the location of a related program that they
have already installed. If you wish to do that, you can call
`AC_PREFIX_PROGRAM'.
- Macro: AC_PREFIX_PROGRAM (PROGRAM)
If the user did not specify an installation prefix (using the
`--prefix' option), guess a value for it by looking for PROGRAM in
`PATH', the way the shell does. If PROGRAM is found, set the
prefix to the parent of the directory containing PROGRAM;
otherwise leave the prefix specified in `Makefile.in' unchanged.
For example, if PROGRAM is `gcc' and the `PATH' contains
`/usr/local/gnu/bin/gcc', set the prefix to `/usr/local/gnu'.
