[sf-perl] Help with Alien::SVN and LD_LIBRARY_PATH
relay at pobox.com
Wed Sep 21 15:25:38 PDT 2011
Does SVN::Core build a Makefile? If you are installing via cpan, try
'look SVN::Core' and look for a Makefile.PL, you'll have to grope
around in there for a LD path setting.
You can also hack it into place in 20 seconds. Linux is setup to cover
the case where lib paths have to be set at runtime - on my sles box:
av:root> cd /etc/ld.so.conf.d/
-rw-r--r-- 1 root root 28 Jul 12 2010 ghostscript-omni.conf
drwxr-xr-x 2 root root 34 May 20 15:05 .
drwxr-xr-x 120 root root 8192 Sep 21 14:31 ..
av:root> cat ghostscript-omni.conf
On all systems you want to run the lib, add a file with just the path
'/path/to/Alien/SVN' and run 'ldconfig'
A different way to hack it is:
Move your lib to a path ld already knows about - this will show you
what's configed on your box:
ldconfig -v |grep :
On Wed, Sep 21, 2011 at 2:58 PM, George Hartzell <hartzell at alerce.com> wrote:
> Hi All, lurkers and regulars,
> I'm working on SLES11 linux systems, Perl 5.14.1.
> I'm trying to achieve something useful that ultimately needs SVN::Core
> to work. SVN::Core is provided by Alien::SVN in my world. As
> Alien::SVN builds it sets LD_RUN_PATH so that it points to its copies
> of the various subversion libraries that it's compiling and they get
> used during the tests.
> It never seems to do anything that ends up pointing LD_RUN_PATH at the
> ultimate installation directory, or setting rpath, or other linker
> black magic before it does the install and the result is that
> perl -MSVN::Core
> fails with the inability to find it's libraries
> I can make it work with (bash worldview)
> export LD_LIBRARY_PATH=/path/to/Alien/SVN
> but I expected that I would not have to do that.
> Does anyone out there in sf.pm land know how this is *supposed* to
> work? Is the requirement to set LD_LIBRARY_PATH what's supposed to
> SanFrancisco-pm mailing list
> SanFrancisco-pm at pm.org
More information about the SanFrancisco-pm