When you built and installed beagle, which directory did you choose for
installation? Did you specify a path with ./configure
--prefix=<installpath> ?
It looks like you ran beast using the beast shell script. That's fine,
but it's not finding beagle wherever it was installed. The shell script
in turn calls java to launch beast, and on the java command-line one
needs to have a -Djava.library.path= setting that gives the path to the
lib directory containing the beagle libs. It's also necessary to have
that same directory listed in the LD_LIBRARY_PATH environment variable
in Linux systems. Sorry if that wasn't obvious. What (if any)
instructions are you following for the beast/beagle usage? Perhaps they
can be fixed to clarify some of these issues.
Incidentally it should really only be necessary to have one working java
compiler, perhaps we can discuss off-list what went wrong that required
installation of all three of gcj, jikes, and sun java.
-Aaron
On Thu, 2010-10-14 at 12:57 -0700, griffinia wrote:
> Aaron, what I don't understand is that I did nothing with the "-
> Djava.library.path=" statement. So Java must be finding the libs
> without it.
I think I may have misspoke earlier when suggesting that both
-Djava.library.path and LD_LIBRARY_PATH need to be set. It seems like
just setting LD_LIBRARY_PATH is sufficient, as also indicated by this
document on Sun's web site:
http://java.sun.com/docs/books/jni/html/start.html