>>>>> "Mike" == Mike Castle <[EMAIL PROTECTED]> writes:
Mike> On Wed, Jul 19, 2000 at 03:14:13PM +0200, Akim Demaille wrote:
>> IOW, what's the point of being able to change prefix at make time?
>> Why not just at configure?
Mike> make prefix=/path/to/install install
Mike> Ie, you want to install into a different area then your built
Mike> for.
Yes, right.
Mike> Or, you are developing code/bug hunting, and you want to build
Mike> for, say /usr/local/test instead of /usr/local.
Then I claim you should reconfigure.
I know one possible use is doing this.
Finally I did what I should have done from the beginning, read the
standards again, and they are extremely clear:
@table @samp
@item prefix
A prefix used in constructing the default values of the variables listed
below. The default value of @code{prefix} should be @file{/usr/local}.
When building the complete GNU system, the prefix will be empty and
@file{/usr} will be a symbolic link to @file{/}.
(If you are using Autoconf, write it as @samp{@@prefix@@}.)
* 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.
