Well, the console is empty as far as this is concerned. And I went through
all the dependencies and everything is there. I also went through and
rebuilt subversion and subversion-javahlbindings in macports. I'm at a bit
of a loss, but I'll keep trying to figure this out in my spare time. Thanks
for your help trying to debug this thing...
On Tue, Sep 9, 2008 at 4:32 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> On Tue, Sep 9, 2008 at 5:08 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> > On Tue, Sep 9, 2008 at 5:03 PM, Mark Phippard <markphip_at_gmail.com>
> >> On Tue, Sep 9, 2008 at 5:00 PM, Troy Daley <tfandango_at_gmail.com> wrote:
> >>> Thanks for all of your help... The results are:
> >>> tdaley-mbp:~ tdaley$ otool -L /opt/local/lib/libsvnjavahl-188.8.131.52.dylib
> >>> /opt/local/lib/libsvnjavahl-184.108.40.206.dylib:
> >> It all looks very normal to me. So not as helpful as I hoped.
> > A colleague informed me that otool -L just displays the library
> > references from the file. On *nix, the ldd tool also attempts to load
> > the libraries and will report the problems.
> > So basically, otool -L is useless for this as a diagnostic tool. I
> > will keep looking for something that will help.
> A brute force technique you could use is to see if each of the named
> dependencies exists. Someone on IRC suggested that the OSX Console
> may also have more information about what library does not load. That
> is in Applications/Utilities.
> If the Console has too much in it, then perhaps open it and run the
> tests again to see which messages get put in again?
> Mark Phippard
Received on 2008-09-10 16:52:11 CEST