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

Re: What hack in ld.so?



On Jan 30, 1999, Jason Gunthorpe <jgg@ualberta.ca> wrote:

> On 30 Jan 1999, Alexandre Oliva wrote:

>> I agree there is a problem to be fixed, I just think that libtool
>> is not the only piece of software that may have to be changed to
>> fix it, because it is not the only piece of software that uses
>> -rpath.

> libtool is however the only piece of software that we cannot easially
> change.

Huh?  You (or someone else, I've (not) been introduced to too many
Debian Developers lately to be able to remember who said what :-(
mentioned editing Makefiles to adapt packages to Debian's policies,
then I said one could just as easily edit the libtool script, and I
have even posted a script that would do that for you.

If you're talking about introducing a quick hack in libtool to never
use rpath, forget about it, it won't work in general.  If you're
willing to contribute a patch to libtool that selectively drops rpath
flags for directories listed in /etc/ld.so.conf, as I have suggested
in another message I posted today, that's great.

> It doesn't really matter who is to blame

Wouldn't the Devian developers complain that libtool isn't not
properly arranging that their programs run even in non-Devian
distributions?  If they were to be as inflexible as you, we'd probably
have to support switches like -devian-hardcoding-policies and
-debian-hardcoding-policies, and I'd certainly have dropped the
maintainership of libtool just after that (or just before)

Thanks God I've got only one group of developers almost forcing me to
change something that is correct, and whose change wouldn't even help
them work around a problem they're facing.

> because it -can- be fixed and fixed fairly easially by the
> installer, the -rpath situation -cannot- be fixed at all by the
> installer, I think that is the key difference to realize.

Ulrich Drepper has already mentioned that it's quite easy to modify
the hard-coded rpath of a program without recompiling it, and that
there's even a tool that will do that.

<joke sarcasm=off skip=(eval $mood==bad)>
It has just occurred to me that you should hack `ld' so that, whenever
it finds a -rpath switch, it prints a warning message like:

*** WARNING: YOU HAVE USED THE NEFAST --rpath SWITCH.  THIS WILL CAUSE
*** YOUR PROGRAM NOT TO WORK ON FUTURE Debian RELEASES BECAUSE WE
*** DON'T CARE ABOUT (L)USERS WHO USE --rpath.  YOU WERE ADVISED!
</joke>

:-D

-- 
Alexandre Oliva  http://www.dcc.unicamp.br/~oliva  aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil


Reply to: