Well, yes, that points to the problem, I think. I have the latest Java JRE 
installed (1.8.51).  If one only has the JRE, then the only way to get the 
latest java on the command line is something like

alias java
java='/Library/Internet\ 
Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java'

(see here: 
http://stackoverflow.com/questions/15624667/mac-osx-java-terminal-version-incorrect)
  
I now get 

java -version
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

But:

/usr/bin/java -version
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)

How does sage find its java, and can I configure that?

Thanks!
Thomas

On Wednesday, August 12, 2015 at 6:32:06 PM UTC+2, Volker Braun wrote:
>
> Which jmol version do you have in homebrew? The newest jmol requires Java8 
> afair. Output of "java -version"?
>
>
>
> On Wednesday, August 12, 2015 at 4:03:48 PM UTC+2, Thomas Kahle wrote:
>>
>> Hi,
>>
>> I use sage-6.8 on the command line and for some time now (like 1 or 2 
>> months) 3d display with jmol does not work anymore.  I get a traceback that 
>> ends in:
>>
>> /Users/tom/sage/local/lib/python2.7/site-packages/sage/repl/rich_output/backend_ipython.pyc
>>  
>> in launch_jmol(self, output_jmol, plain_text)
>>     363         jdata = JmolData()
>>     364         if not jdata.is_jvm_available() and not DOCTEST_MODE:
>> --> 365             raise RuntimeError('jmol cannot run, no suitable java 
>> version found')
>>     366         launch_script = output_jmol.launch_script_filename()
>>     367         from sage.env import SAGE_LOCAL
>>
>> RuntimeError: jmol cannot run, no suitable java version found
>>
>> Java is installed on this machine, and I think it is working correctly 
>> evidenced by the following facts
>>
>> -) I can run 3d plots in the browser using the sage notebook.
>> -) I can install and run jmol via homebrew with no problems.
>>
>> Just when it is started through command line sage, it won't work. How can 
>> I debug this?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to