It sounds like you have some other svn libs elsewhere (and hashed
earlier) in your loader path. Do you have a Solaris pkg or rpm already
installed for subversion?
Of course this all becomes moot if you use the lovely javasvn client.
Even if you have a file:/// repository, running a local svnserve process
and using javasvn is a whole lot easier than getting the javahl voodoo
to work on *nix.
Cheers,
Dan
Ken Nakamura wrote:
>Hello,
>
>I'm not sure if this is the right place for this question. It's an odd
>occurrence...
>
>I have built my own svn-1.2.3, with javahl enabled. I'd like svnant to
>use javahl; not that I don't like javasvn (props to alex k, it rocks),
>but according to subclipse's faq, javahl sounds like the best way. I'm
>on Solaris 9 and the svn libs are in /usr/local/lib, which I've added to
>the LD_LIBRARY_PATH using 'crle'. This means that it's not actually an
>environment variable, but stashed in a file, /var/ld/ld.config. ld.so
>is supposed to parse it and dynamically load libs accordingly. From
>what I can tell, this is the Solaris Way. Here's the problem:
>
>If I *don't* specifically export LD_LIBRARY_PATH into my environment,
>svnant doesn't find the libs and resorts to javasvn. I've run the test
>ant script through truss and note that it tries to stat64
>libsvnjavahl-1.so in several locations that aren't in LD_LIBRARY_PATH,
>like lib dirs under my JAVA_HOME/jre tree. I find that odd...
>
>So, is this a weird svnant issue? Is it the jvm? Is it my box? Is it
>even really worth using javahl over javasvn, now that javasvn is at 1.0?
>Should I just not care and export the lib path in my .bash_profile?
>
>-k
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
>For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
Received on Fri Nov 11 09:43:16 2005