Thanks!
On Wed, May 23, 2012 at 4:38 PM, Ralph Castain wrote:
> It did, however, serve one purpose - it made me look closer at the
> Java-related configury and find an error (we were -always- building Java
> bindings).
>
> I added the flag Josh mentioned, so --disable-java will turn off *all*
It did, however, serve one purpose - it made me look closer at the Java-related
configury and find an error (we were -always- building Java bindings).
I added the flag Josh mentioned, so --disable-java will turn off *all*
Java-related code.
Thanks Josh
On May 23, 2012, at 2:31 PM, Josh Hursey
To follow up on this thread for the list. I can no longer reproduce
this configure error. It existed, really it did... :/
After a maintenance cycle on the machine and updating to the current
trunk all was fine. The configure logic in the trunk did the right
thing. When it did not find a java compi
Thanks. I figured it was just overlooked since most systems have a
java compiler installed in normal locations these days.
-- Josh
On Wed, May 23, 2012 at 8:56 AM, Ralph Castain wrote:
> I'll fix that - yes, you should be able to build if no Java compiler is found.
>
>
> On May 23, 2012, at 6:51
I'll fix that - yes, you should be able to build if no Java compiler is found.
On May 23, 2012, at 6:51 AM, Josh Hursey wrote:
> Is there a way to build Open MPI without a Java compiler?
>
> Meaning, I have no Java compiler on a particular machine, and
> '--disable-mpi-java' disables only the J
Is there a way to build Open MPI without a Java compiler?
Meaning, I have no Java compiler on a particular machine, and
'--disable-mpi-java' disables only the Java bindings and not the Java
compiler check. If the Java compiler check fails to find a compiler
then configure currently fails.
-- Josh
