[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2006-03-25 14:55:40 CET

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

> Sorry for the repost, but the Perl modules have been broken for such a
> long time. Please apply, or tell me what is wrong with it.
> I see no way this could be worse than what already is, in any case.
>
> [[
> Give Perl modules the correct run-time path (issue 2479); they should use
> the installation directory, not just the build directory.
>
> * subversion/bindings/swig/perl/native/Makefile.PL.in
> Add libdir first in the run-time path.
> ]]
>
> Index: subversion/bindings/swig/perl/native/Makefile.PL.in
> ===================================================================
> --- subversion/bindings/swig/perl/native/Makefile.PL.in (revision 18963)
> +++ subversion/bindings/swig/perl/native/Makefile.PL.in (working copy)
> @@ -14,9 +14,13 @@
> my $svnlib_builddir = "${top_builddir}/subversion";
> my $swig_srcdir = "${svnlib_srcdir}/bindings/swig";
> my $swig_builddir = "${svnlib_builddir}/bindings/swig";
> +my $prefix = '@prefix@';
> +my $exec_prefix = "@exec_prefix@";
> +my $libdir = "@libdir@";
>
> my @modules = qw/client delta fs ra repos wc/;
> -my @ldpaths = ("$swig_builddir/perl/libsvn_swig_perl/.libs",
> +my @ldpaths = ($libdir,
> + "$swig_builddir/perl/libsvn_swig_perl/.libs",
> map {"$svnlib_builddir/libsvn_$_/.libs"} (@modules, qw/diff subr
> ra_local
> ra_svn

Does this affect the regression tests? Will the regression tests use
installed objects instead of those in the build tree?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 25 14:56:06 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.