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 compiler/libs in the search paths
it skipped over it and moved on. I'm still not sure what changed, I
credit the maintenance cycle.
On Wed, May 23, 2012 at 9:08 AM, Josh Hursey <jjhursey_at_[hidden]> wrote:
> 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 <rhc_at_[hidden]> 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 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 Java bindings and not the Java
>>> compiler check. If the Java compiler check fails to find a compiler
>>> then configure currently fails.
>>> -- Josh
>>> Joshua Hursey
>>> Postdoctoral Research Associate
>>> Oak Ridge National Laboratory
>>> devel mailing list
>> devel mailing list
> Joshua Hursey
> Postdoctoral Research Associate
> Oak Ridge National Laboratory
Postdoctoral Research Associate
Oak Ridge National Laboratory