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

Re: cvs2svn fails to parse certain RCS files

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2002-09-22 07:59:25 CEST

On Sat, 21 Sep 2002, Will Andrews wrote:

> On Sun, Sep 22, 2002 at 12:40:51AM -0500, David Summers wrote:
> > It wasn't enable before but it was detecting the SWIG 1.3.15 but I just
> > added --with-swig to the Subversion ./configure but it doesn't seem to
> > make any difference. I'm still getting the above error.
>
> Did you re-build and re-install the swig bindings after you
> re-installed subversion with swig support?

Hmmm. I think so. I'm trying to modify my Subversion RPMs to include the
ability to use the cvs2svn python script. So during the build of
Subversion I try to tell it to also build and install the subversion swig
bindings so it can run cvs2svn.

If I'm following your line of questioning, trying to anticipate where this
is leading then my question is: Does Subversion have to be installed in
its final place BEFORE the swig binding can be compiled? It appears that
it compiles OK even before the subversion is installed but maybe I'm
missing something. If Subversion has to be installed BEFORE the swig
bindings can be compiled and used then I guess I'll have to make a
separate package....that would be a bit of a bummer but I'll do whatever
it takes to get this working. I was hoping to have it all built in one
RPM.

   Thanks

-- 
David Wayne Summers          "Linux: Because reboots are for upgrades!"
david_at_summersoft.fay.ar.us   PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  C0 E0 4F 50 DD A9 B6 2B  60 A1 31 7E D2 28 6D A8 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Sep 22 08:00:48 2002

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.