This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Installation proposal
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: Richard Henderson <rth at redhat dot com>, Tom Tromey <tromey at redhat dot com>, Mark Mitchell <mark at codesourcery dot com>, <gcc at gcc dot gnu dot org>
- Date: 28 Feb 2002 07:02:18 -0300
- Subject: Re: Installation proposal
- Organization: GCC Team, Red Hat
- References: <Pine.LNX.4.33.0202280943100.23324-100000@kern.srcf.societies.cam.ac.uk>
On Feb 28, 2002, "Joseph S. Myers" <jsm28@cam.ac.uk> wrote:
> On 27 Feb 2002, Alexandre Oliva wrote:
>> - on most other systems, when a libtool shared library is linked with
>> another libtool shared library, the latter still being in its build
>> tree. Because libtool creates libraries in the build tree in such a
>> way that they can be linked with and used in-place, it encodes
>> build-tree pathnames into the library. Then, at install time, it
>> re-links libraries such that the work in the install tree. Again,
>> on HP-UX, DESTDIR installations don't work.
> libtool also encodes build tree paths into the .la files it installs (e.g.
> PR other/3525). Why don't those get properly regenerated at install time?
Because libtool can't possibly know when an -L flag refers to a
build-tree pathname or to an install-tree pathname unless some
mechanism to tell it so is introduced in it.
> Is there a security issue here?
Yes.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer