[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why relink the library during make install?
From: |
Russ Allbery |
Subject: |
Re: Why relink the library during make install? |
Date: |
Wed, 24 Jul 2002 14:21:58 -0700 |
User-agent: |
Gnus/5.090005 (Oort Gnus v0.05) XEmacs/21.4 (Honest Recruiter, sparc-sun-solaris2.6) |
Bruno Haible <address@hidden> writes:
> This only means that the one who does
> 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.
This works for every other GNU package that I've built, it is required by
the GNU Coding Standards, and it worked for the previous version of
gettext. I don't understand why you're breaking this.
--
Russ Allbery (address@hidden) <http://www.eyrie.org/~eagle/>
- Why relink the library during make install?, Paul Lew, 2002/07/24
- Re: Why relink the library during make install?, Thomas Bushnell, BSG, 2002/07/24
- 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