On 9/25/07, John Peacock <john.peacock@havurah-software.org> wrote:
> Miller, Eric wrote:
> > Yeah, tried that:
> >
> > % rm -rf subversion/bindings/swig/perl/native/*.c
> >
> > % make swig-pl
> > make: *** No rule to make target
> > `subversion/bindings/swig/perl/native/core.c', needed by
> > `autogen-swig-pl'. Stop.
>
> Did you try this sequence?
>
> ./configure --with-swig
> make
> make swig-pl
>
> It may be that the swig targets are not completely independent (i.e.
> some elements needed by swig-pl are only generated when you run make
> after enabling swig). I always build in sequence make, make swig-py,
> make swig-pl, so I'm not sure this is the correct fix, but it wouldn't
> surprise me in the least.
This isn't the problem. The problem here is that the user didn't run
'autogen.sh' to switch the SWIG bindings from release mode to
development mode. In release mode, you use the SWIG bindings shipped
with the release. OTOH, if you're in development mode, Subversion will
generate the SWIG bindings using the version of SWIG you have
installed.
Cheers,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 27 02:00:11 2007