On Nov 12, 7:08 pm, Mitesh Patel <[email protected]> wrote: > On 11/12/2010 08:29 PM, Mike Witt wrote: > > > > > On 11/12/2010 05:49:49 PM, Mitesh Patel wrote: > >> On 11/12/2010 06:43 PM, Mike Witt wrote: > >> > On 11/12/2010 04:14:29 PM, Mitesh Patel wrote: > >> >> On 11/12/2010 05:48 PM, Mike Witt wrote: > >> >> > After a new Fedora 14 installation, I ended up with the "default" > >> >> > version of Java they use (IdedTea?) -- This didn't work for > >> >> > Sage/JMOL, either on the command line or in the Notebook. So, I > >> >> > installed the Oracle version. But both versions are now installed. > >> >> > I figured out how to tell Firefox to use the Oracle version, and > >> >> > now JMOL works fine in a notebook. But from the sage command line > >> >> > it's still not working. > > >> >> > So, I suspect that the sage command line is still calling the > >> >> > other version of Java. Is there any way I can check what path > >> >> > it's using? > > >> >> Could you check the symbolic link /etc/alternatives/java? What happens > >> >> if you make this point to /path/to/oracle/java/bin/java? > > >> > I believe it's correct: > > >> > [m...@vector ~]$ /usr/bin/java -version > >> > java version "1.6.0_22" > >> > Java(TM) SE Runtime Environment (build 1.6.0_22-b04) > >> > Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode) > > >> > However, it was pointing to the IcedTea java when I built > >> > Sage. I just wondered if perhaps that got "cached" somehow. > >> > I guess that seems unlikely. Maybe the lack of 3d display > >> > from the command line is an unrelated problem? > > >> Which Sage version are you using? > > >> Making a Jmol plot on the command-line invokes > > >> SAGE_LOCAL/bin/jmol > > >> Maybe JMOL_HOME is set incorrectly in this script? What happens if > >> you put > > >> JMOL_HOME="/explicit/path/to/sage_root/devel/sagenb-main/sagenb/data/jmol" > > >> near the top? > > > Well, yes, that seems to be it. It took me a bit to figure out > > what to do, but now that I found the script ... as far as I can > > tell, JMOL_HOME was getting set to: /sagenb/data/jmol > > > When I reset it, as you suggested, at the top of the script > > then everything started working (from the command line). So, > > it does appear that they were two separate problems. > > > Oh, I'm using 4.6. If this is already a known issue, then > > my apologies. But thanks very much for the solution! > > Does anyone else have this problem?
FYI, I had built 4.6 on both FC-11 and FC-12 and this phenomenon did not occur on either of those systems. So I bet it's either some quirk of FC-14, or else some thing weird that I somehow did. Also, the same thing happens when I run 4.5.1 on this FC-14 install. So, it's definitely not anything to do with sage 4.6. -Mike -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
