From: | Trond Eivind Glomsrød <teg(at)redhat(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 7.2b2 "make check" failure on Red Hat Linux 7.2 |
Date: | 2001-11-18 16:45:24 |
Message-ID: | Pine.LNX.4.33.0111181141570.16070-100000@halden.devel.redhat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 18 Nov 2001, Peter Eisentraut wrote:
> Trond Eivind Glomsrød writes:
>
> > Fix? Don't use rpath - it's evil, and should be avoided anyway.
>
> configure --disable-rpath is your friend.
Didn't know about that one - it will certainly be put to use :)
> Overall, rpath gives us much more benefit than the occasional trouble it
> creates.
When you install (not configure for, just install) into a separate tree
(for easier packaging), it's a hole which can be exploited - some packages
will rpath into /var/tmp/<foo>, for instance. Hackers can then put their
own library there. One big offender here is perl's automatic module
creation script which will change the rpaths from what you told it when
you built it to what you do when you install it.
--
Trond Eivind Glomsrød
Red Hat, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-11-18 17:17:24 | Re: TODO item inquiry/claim |
Previous Message | Peter Eisentraut | 2001-11-18 16:42:37 | Re: 7.2b2 "make check" failure on Red Hat Linux 7.2 |