From: Chip Turner Date: Sun, 5 Jan 2003 10:35:40 +0000 (-0500) Subject: Re: Shared libperl.so and build issues X-Git-Tag: accepted/trunk/20130322.191538~24657 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1ff4263c2be000d5dd4e3ae4643d6c34358e9dce;p=platform%2Fupstream%2Fperl.git Re: Shared libperl.so and build issues Message-ID: p4raw-id: //depot/perl@18874 --- diff --git a/INSTALL b/INSTALL index 08e7dd8..e7508af 100644 --- a/INSTALL +++ b/INSTALL @@ -937,9 +937,10 @@ libperl.so.8 rather with the installed libperl.so.8? The answer is that you might not be able to. The installation directory is encoded in the perl binary with the LD_RUN_PATH environment variable (or equivalent ld command-line option). On Solaris, you can override that -with LD_LIBRARY_PATH; on Linux you can't. On Digital Unix, you can -override LD_LIBRARY_PATH by setting the _RLD_ROOT environment variable -to point to the perl build directory. +with LD_LIBRARY_PATH; on Linux, you can only override at runtime via +LD_PRELOAD, specifying the exact filename you wish to be used; and on +Digital Unix, you can override LD_LIBRARY_PATH by setting the +_RLD_ROOT environment variable to point to the perl build directory. The only reliable answer is that you should specify a different directory for the architecture-dependent library for your -DDEBUGGING