This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: [PATCH] ppc64 LD_PRELOAD tolerance
- From: Ulrich Drepper <drepper at redhat dot com>
- To: Steve Munroe <sjmunroe at us dot ibm dot com>
- Cc: Roland McGrath <roland at redhat dot com>, libc-alpha at sources dot redhat dot com, libc-alpha-owner at sources dot redhat dot com, Steve Munroe <sjmunroe at vnet dot ibm dot com>
- Date: Thu, 26 Sep 2002 11:22:35 -0700
- Subject: Re: [PATCH] ppc64 LD_PRELOAD tolerance
- References: <OF69CBE588.3625CD58-ON86256C40.004ADB10@rchland.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steve Munroe wrote:
> Perhaps some addition dynamic symbols can improve this. For example
> ($LIB32)my.so indicates explicitly that my.so only exists for 32-bit and
> should be ignored for 64-bit. Of ($skip64)my.so could be added to the end
> of the LD_PRELOAD string to recover from the first scenario.
No. We are not going to add an own programming language to the
LD_PRELOAD handling. If you need a DSO only for 32-bit create a dummy
for 64-bit. This is no problem since LD_PRELOAD should never be used
lightly; it should always and only be used in invocations of one
program. It mustn't be in the environment and exported. LD_PRELOAD is
means for temporary work arounds and testing etc. If you need it to get
a program running write a shell script wrapper which uses LD_PRELOAD.
But that's it.
- --
- ---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9k1Br2ijCOnn/RHQRAqimAKCyT7EsNt/Fvq8lErldbJFbJ5YnewCgxOv3
egRV3iAQrM9NTRqa7oppi+s=
=gOsx
-----END PGP SIGNATURE-----