Re: [PATCH] Correct path to Perl modules (issue 2479)

Mattias Engdegård <mattias@virtutech.se> writes:

> Unless, of course, everyone configure with --prefix=/usr (which I don't).
> In which case there is room for surprise when someone builds new
> modules using the same build path.

The perl bindings didn't get installed into --prefix when I last tried
to install them (some time ago admittedly), I would have needed to use
root to write into the perl tree. For that reason I've never
installed the perl bindings but I have installed the python bindings
which do install into --prefix.

>>I wish I had the time to go through the Perl binding in detail and
>>rework them to use a regular makefile and libtool (just for
>>convenience's sake for the rest of the project) so the bindings would
>>get linked to the right library all the time automatically. It may be
>>that using appropriately shaped LD_LIBRARY_PATH would do the job instead.
>
> Using LD_LIBRARY_PATH for testing is a good idea (if linking with
> --enable-new-dtags on Linux). For locating the installation libdir,
> LD_LIBRARY_PATH is much less attractive.

Using LD_LIBRARY_PATH for testing, putting the install directory in
rpath (only if it's non-standard perhaps?), and removing the build dir
from rpath all sound like good ideas, although there are portability
concerns.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org