Re: Why relink the library during make install?

[Thomas Bushnell, BSG]

Bruno Haible <address@hidden> writes:

>    configure --prefix=/A
>    make
>    make install prefix=/B
> 
> cannot expect that auxiliary files (in lib, share, doc, etc) will
> be found. The "make" process has no chance to put the pathnames
> /B/lib, /B/share etc. into the executables and libraries because it
> doesn't know about /B at that moment. In most cases, the installed
> package will not run.

Exactly the purpose of that sequence of commands.  The commands should
look for their tools in /A, and they should not expect to work as
installed into /B.  Users use command sequences like this precisely
when they expect to make the binaries appear--at some later date--at
/A.