You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ross <rs...@triad.rr.com> on 2005/03/29 01:56:41 UTC

Ruby bindings problems

I found two possible issues concerning the Ruby bindings that are now in 
the trunk. I'm not sure if these are bugs, or if there is something that 
I missed during configuration/compilation, but I'll try and describe 
what I found.

Summary:
--------

(1) the *.rb files in subversion/bindings/swig/ruby/svn do not appear to 
be copied into site_ruby, so when running a script such as 
tools/examples/svnlook.rb, the Ruby interpreter reports that the 
required files (such as "svn/core") cannot be loaded.

(2) Two tests fail when I run `make check-swig-rb`.

Software versions:
------------------

Subversion r13709
SWIG 1.3.24
Ruby 1.8.2

Steps I took:
-------------

I configured Subversion --with-swig providing the path to SWIG-1.3.24. 
After making Subversion successfully, I executed these commands:

make swig-rb
make check-swig-rb
make install-swig-rb

Two tests failed. I have attached the entire output of check-swig-rb to 
this email. The failed test names are "test_change_prop(SvnDeltaTest)" 
and "test_authentication(TestSvnClient)".

Although two tests failed. I went ahead with install-swig-rb. Install 
appeared to go okay (Ruby libraries installed in 
lib/ruby/site_ruby/1.8/i686-linux/svn/ext/). However, when I ran 
tools/examples/svnlook.rb, I got a Ruby interpreter error saying that 
the first required file ("svn/core") could not be found. I searched 
through my Ruby directory and I could not find svn/core.rb.

So, I copied the contents of subversion/bindings/swig/ruby/svn to 
lib/ruby/site_ruby/1.8/svn inside my ruby directory. After doing so, 
svnlook.rb seemed to work fine. I re-ran check-swig-rb, but the same two 
tests still failed.

---

Thanks to all the people who work on Subversion, your expertise and time 
are very much appreciated. I hope that this report is helpful. I'll be 
happy to provide whatever follow-up information I can.

Ross Shaull
ross@simanage.com