> On Oct 24, 2014, at 1:31 PM, Philip Martin <philip.mar...@wandisco.com> wrote:
> "Daniel J. Luke" <dl...@geeklair.net> writes:
>>> Does this work:
>>>
>>> svnadmin create repo
>>> svn import -mm repo/format file://`pwd`/repo/f
>>> sqlite3 repo/db/rep-cache.db "select * from rep_cache"
>>>
>>> The sqlite3 command should show a single line such as:
>>>
>>> 5d9474c0309b7ca09a182d888f73b37a8fe1362c|1|0|14|2
>>
>> yes, this works and gives that result (but subversion itself passes
>> its test when built/run by macports, so I would expect it to work).
>
> I don't understand OSX terminology. Are you claiming that the command
> line binaries work and the JavaHL bindings fail?
yes - but there is something about the MacPorts build that is causing this (I
maintain the macports 'port' of subversion and language bindings).
MacPorts builds the command line binary + libraries which install and run fine
(like that have since pre 1.0). I can run the test suite (make check) from
within MacPorts and it works.
MacPorts builds the javahl bindings (libsvnjavahl-1.dylib, svn-javahl.jar and
their various symlinks) separately. It used to be able to run and pass passes
its test suite (make check-javahl).
I upgraded my main machine to Yosemite (Mac OS X 10.10) and installed java
1.8.0_25 and now while the MacPorts build looks like it works, the test suite
fails (and people who use the bindings with eclipse have said that it crashes).
If I build outside of MacPorts it works for me, which is odd. The MacPorts
build uses a non-privildeged user and does some environment sanitization, but
not anything crazy. I'll do some more looking to see if I can figure out what
may be causing it - but it's very strange.
> The JavaHL bindings
> use the same libraries to access the code as the commmand line clients.
> If one works and the other does not it implies that the different
> libraries are getting loaded at runtime. I have no idea what you need
> to do to get the correct libraries to load on OSX.
make check-javahl sets DYLD_LIBRARY_PATH so the libraries from the build take
precedence over any others. I'll check to see which library(s) are getting
loaded at runtime both from the MacPorts build and my non-MacPorts build and
see if there's anything there. Thanks for giving me some place to start...
--
Daniel J. Luke
+========================================================+
| *---------------- dl...@geeklair.net ----------------* |
| *-------------- http://www.geeklair.net -------------* |
+========================================================+
| Opinions expressed are mine and do not necessarily |
| reflect the opinions of my employer. |
+========================================================+
