>>>>> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> Why can't we set prefix to /usr/local and exec_prefix to ${prefix}
Mo> unless it differs from prefix? It is getting set in ./configure it
Mo> is just a matter of when.
The only place were we rely on it is
# AC_PREFIX_PROGRAM(PROGRAM)
# --------------------------
# Guess the value for the `prefix' variable by looking for
# the argument program along PATH and taking its parent.
# Example: if the argument is `gcc' and we find /usr/local/gnu/bin/gcc,
# set `prefix' to /usr/local/gnu.
# This comes too late to find a site file based on the prefix,
# and it might use a cached value for the path.
# No big loss, I think, since most configures don't use this macro anyway.
AC_DEFUN([AC_PREFIX_PROGRAM],
[dnl Get an upper case version of $[1].
pushdef(AC_Prog, translit($1, a-z, A-Z))dnl
if test "x$prefix" = xNONE; then
dnl We reimplement AC_MSG_CHECKING (mostly) to avoid the ... in the middle.
echo $ECHO_N "checking for prefix by $ECHO_C" >&AC_FD_MSG
AC_PATH_PROG(AC_Prog, $1)
if test -n "$ac_cv_path_[]AC_Prog"; then
prefix=`echo $ac_cv_path_[]AC_Prog | [sed 's,/[^/][^/]*//*[^/][^/]*$,,']`
fi
fi
popdef([AC_Prog])dnl
])# AC_PREFIX_PROGRAM
A quick glance seems to show that we can get rid of all the others.
Here we make a difference between `the user did not set prefix' and
`the user specified the default prefix as prefix'.
Is this macro really useful?
