[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why relink the library during make install?
From: |
Thomas Bushnell, BSG |
Subject: |
Re: Why relink the library during make install? |
Date: |
24 Jul 2002 15:51:58 -0700 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 |
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.
- Why relink the library during make install?, Paul Lew, 2002/07/24
- Re: Why relink the library during make install?, Bruno Haible, 2002/07/24
- Re: Why relink the library during make install?, Paul Lew, 2002/07/24
- Re: Why relink the library during make install?, Alfred M. Szmidt, 2002/07/24
- Re: Why relink the library during make install?, Russ Allbery, 2002/07/24
- Re: Why relink the library during make install?, Ralph Corderoy, 2002/07/31
- Re: Why relink the library during make install?, Miles Bader, 2002/07/31
- Re: Why relink the library during make install?,
Thomas Bushnell, BSG <=
- Re: Why relink the library during make install?, Miles Bader, 2002/07/25
- Re: Why relink the library during make install?, Albert Chin, 2002/07/25
- Re: Why relink the library during make install?, Albert Chin, 2002/07/25
- Re: Why relink the library during make install?, Miles Bader, 2002/07/25
- Re: Why relink the library during make install?, Albert Chin, 2002/07/26
- Re: Why relink the library during make install?, Russ Allbery, 2002/07/26