![]() There is, however: "Source tarball (.tar.gz) for compilation under Unix (including Linux and MacOS X) and Microsoft Windows (including Cygwin)." Dead End: Trying OCaml 3.09 Binary Possible Solution: Try OCaml 3.09 Binary Unfortunately the precompiled binaries for Mac (Intel or PPC) were "compiled on Mac OS 10.5.5 with XCode tools v3.1.1 (not compatible with Mac OS 10.4.x)," a slightly ambiguous statement but I concluded the binaries (as opposed to XCode tools v3.1.1) were not compatible with Tiger. Getting the compiler running turned out to be a bit of a challenge as the latest version wasn't compatible with my OS.Īccording to, "The most recent version of Objective Caml is 3.11.0. The first task was to get the OCaml compiler working before I could try compiling the Jape source code. Problem: OCaml 3.11 binary doesn't work with Tiger Richard Bornat suggested I compile from the source code for Jape written in OCaml, but this required some preliminary steps. I did some more exploring and discovered that older versions up to 7.4.11 (I didn't try them all) seemed to work while 7.5.1a and beyond brought up the same error message as the latest versions. One possibility is that Java isn't being so universal as it might claim to be (I'm running Java 2 version 1.5.0_16), or there could be an OCaml issue. Richard Bornat promptly replied to an E-mail and noted that there was a GUI portion (written in Java) and a Jape engine (written in OCaml). ![]() At one point I restarted the laptop and I got to the point where I could explore all the "Jape" menu choices, but the "About Jape" (which shows the version) was the only choice not greyed out (aside from the general Mac OSX menu choices such as "Services").Ĭould it be a problem that I'm running Tiger not Leopard? Suggestion: Compile Jape Source Code Possible Solution: Compile Jape I tried both the latest version of Jape and the second-last version. I'm using an Intel MacBook Pro that's two or three years old, Mac OS X10.4.11, and the latest update for Java ("Java for Mac OS X 10.4, Release I downloaded the latest Jape binary for Mac OSX, but when I attempted to start up Jape 7.6.4 (or 7.6.3) on my Mac (running Tiger) I would get the GUI error message, "Dispatcher sees null line - is jape_engine ok?" Choosing "Continue" just brought up the error window again. Jape says: "Dispatcher sees null line - is jape_engine ok?" Once the problem is solved I'll shorten the article even more to concentrate on the germane points. There is still some infelicitous wording including inconsistent tense, and my formatting needs some work. I'm editing this entry to make it better organized and less of the rambling "real time" journal it started off as. Meantime, there's a new how-to-build file for OS X which acknowledges the problem and at least tells you what to do with JarBundler. Jeff Lindstrom pointed out that (a) Jape doesn't run on OS X 10.4 and (b) it doesn't even build on 10.4. (2nd Feb 2009) Mac OS X stuff again (sigh!). Richard Bornat notes on the Jape Web site: I also confirmed that the latest Jape doesn't run on a PPC Mac. This article lists some of the problems that arose and some solutions I tried (with considerable help from Richard Bornat).Ĭuriously some older versions of Jape (written before Leopard's introduction) also didn't run on the MacBook Pro, which may mean it's a problem specific to my laptop or with a particular version of Java, and not the fact that I'm not running Leopard. I couldn't get the precompiled binary to run on Mac OSX 10.4.11. I wanted to try out Jape, a proof helper (available at ) designed and maintained by Richard Bornat, with the latest versions compiled using OCaml. ![]() I assume will soon add this version for download. Bornat sent me a new version compiled by his collaborator, Bernard Sufrin, and it worked fine. Jape now works on Tiger (Apple's Mac OS X 10.4).
0 Comments
Leave a Reply. |