develooper Front page | perl.perl5.porters | Postings from March 2003

Re: Shared and build issues

Thread Previous | Thread Next
Stas Bekman
March 8, 2003 22:32
Re: Shared and build issues
Message ID:
Chip Turner wrote:
> Andy Dougherty <> writes:
>>One request:  Could you also patch up the INSTALL file where it talks
>>about installing shared perl libraries of different "flavors" to include
>>the LD_PRELOAD trick?  (Currently, it says you can't get around
>>LD_RUN_PATH on Linux.)
> Sure thing.

Any reason why Chip's patches were applied? At least the doc one (re-attached 

I for myself has obtained a habit of doing 'make install && make test' (and 
not the other way around) on the blead perls because too many times 'make 
test' would fail because the installed gets loaded instead of the 
new one, yet uninstalled.

--- perl-5.8.0/INSTALL.linuxfix	2003-01-05 10:28:06.000000000 -0500
+++ perl-5.8.0/INSTALL	2003-01-05 10:34:24.000000000 -0500
@@ -937,9 +937,10 @@
  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

Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker     mod_perl Guide --->

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About