Usually, we have daily SVN (Subversion) snapshots and publicly accessible Subversion repository:
See http://sablevm-shot.dyndns.org/ for snapshots and INSTALL.txt
But, the machine died yesterday, so *.tar.gz snapshots will be unavailable for a very short while (a day or two). You you can retrieve a snapshot directly out of the Subversion repository.
Our latest snapshot of the "staging" branch of sablevm & sablevm classpath include a merge with GNU Classpath 0.07. [Along with many other things, like very recent (yesterday) change of default PowerPC interpreter engine to inline-threaded].
To get the snapshit, you simply need to install Subversion (http://subeversion.tigris.org/) [Debian: "apt-get install subversion"], then you can type:
$ svn co svn://svn.sablevm.org/sablevm/branches/staging sablevm $ svn co svn://svn.sablevm.org/sablevm-classpath/branches/staging sablevm-classpath $ cd sablevm $ ./autogen.sh $ cd ../sablevm-staging $ ./autogen.sh $ cd ..
That's it. From there, if you want to build sablevm, you can follow David Belanger's instructions (exception: DO NOT SET JVM_REFERENCE) in: http://sourceforge.net/mailarchive/forum.php?thread_id=3519087&forum_id=4154
Note that to get David's build_classpath script, you should type the following:
$ svn cat svn://svn.sablevm.org/developers/belanger/sandbox/sablejit-classpath/bin/build_classpath > build_classpath $ chmod u+x build_classpath
If you modify sablevm or sablevm-classpath, you can extract a patch file by doing the following:
$ svn info ## please include the output of "svn info" in your message to the ## sablevm-devel mailing list. $ svn diff > patchfile ## attach patchfile to your message to the sablevm-developer mailing-list
Have fun!
Etienne
-- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
