[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: -rpath with libtool and Debian Linux

> -----Original Message-----
> From: Alexandre Oliva [mailto:oliva@dcc.unicamp.br]
> Sent: Wednesday, February 03, 1999 12:01 PM
> To: Jules Bean
> Cc: Ian Lance Taylor; jgoerzen@complete.org; jdassen@wi.leidenuniv.nl;
> debian-devel@lists.debian.org; yosh@gimp.org; bug-libtool@gnu.org;
> libtool@packages.debian.org
> Subject: Re: -rpath with libtool and Debian Linux
> On Feb  3, 1999, Jules Bean <jmlb2@hermes.cam.ac.uk> wrote:
> > On Tue, 2 Feb 1999, Ian Lance Taylor wrote:

> > I really don't see why it's clever to hardcode paths...
> I think the point is that they can't hurt (or couldn't, before the bad
> transition from libc5 to glibc), and selectively dropping them
> requires additional code, which nobody has ever implemented.

To be right you have to say: They shouldn't hurt. The problem is that
they *do* hurt... Anyway I think we've reached a consesus to not use
-rpath on system directories (that is directories that get searched by
default) and that seems perfectly reasonable.

I can *not* expect the linker to be able to resolve problems with
libraries he do *not* know and I do *not* ask for a system that will
allow a program built on some specially tailored system (that is one
where I've added a lot of new "system" directories) to work on standard
systems. After all if I mess up my system, it's my fault...



Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com

Reply to: