On 19 Jul 2000, Russ Allbery wrote:
> Akim Demaille <[EMAIL PROTECTED]> writes:
>
> > * Running @samp{make install} with a different value of @code{prefix}
> > * from the one used to build the program should @var{not} recompile
> > * the program.
>
> > This is all I wanted to know. Just don't use make install prefix=/foo
> > unless you want some more fun or know for sure the package hard codes no
> > path.
>
> Or unless you're using AFS, which requires installations into a different
> set of directories than the programs will run out of due to the way
> replication is handled, or unless you're using one of the many package
> management systems that want things installed in their own directories and
> then make symlinks into /usr/local.
>
> Admittedly, my experience is a bit unusual, but for me setting prefix at
> make install time is the *common* case (and packages that don't hard-code
> all their paths with make and *only install* with make install annoy me no
> end).
I think the common case for almost everyone is "./configure ; make install"
Doing an install into a different directory than you configured
for may be possible with some packages, but I don't think it
is the common case.
Has anyone come up a reason why setting the ${prefix} and ${exec_prefix}
variables at the top of ./configure would be bad?
Mo DeJong
Red Hat Inc
