On 19 Jul 2000, Akim Demaille wrote:
> | Does anyone else find that rather odd? I would like to
> | be able to set vars that I am going to subst based on
> | ${prefix} and ${exec_prefix}, but it seems that nasty
> | hacks like the following are required in my configure.in.
>
> "" is a valid value for those variables, we need something else to
> know they have no value.
Why can't we set prefix to /usr/local and exec_prefix to ${prefix}
unless it differs from prefix? It is getting set in ./configure
it is just a matter of when.
> | if test "${prefix}" = "NONE"; then
> | prefix=/usr/local
> | fi
> | if test "${exec_prefix}" = "NONE"; then
> | exec_prefix=$prefix
> | fi
>
> Yep, this sucks, but I think we have to leave with that.
>
> Anyway, you are not supposed to depend on those variables but from the
> Makefile, which will handle all the evaluations. If you need to, see
> AC_EXPAND_DIRNAME or so, from Alexandre, in the Autoconf Macro
> Archive, but keep in mind this goes against the GNU Std: they say you
> can change your mind between configure and make:
>
> ./configure prefix=toto
>
> make prefix=/usr/local
That will not work. I need to generate a tclConfig.sh file
that stores the variables and path stuff found at ./configure
time. If you go change this stuff in the Makefile, the
generated tclConfig.sh.in is not going to get that updated
info. I think the Gnu docs need to be fixed in this respect.
> This sucks too :( IMHO, it should not be possible, and maybe it is
> now obsoleted by DESTDIR?
Mo DeJong
Red Hat Inc
