Skip to content


Subversion checkout URL

You can clone with
Download ZIP
The Kaffe Virtual Machine
C Shell Java C++ Perl Objective-J Assembly
Latest commit 9c61a68 1 @penberg penberg Merge pull request #3 from javierguzman/master
Tile64 support added
Failed to load latest commit information.
FAQ removed old kaffe awt implementations
compat-include Updated FSFs address all over the place
config Tile64 support added
developers removed version checking logic from
docs Updated FSFs address all over the place
include Use autoreconf to bring 'configure' up-to-date
kaffe Use autoreconf to bring 'configure' up-to-date
libraries Fix compilation errors in 'java.lang.reflect' classes
m4 Use autoreconf to bring 'configure' up-to-date
po removed binreloc support
replace Use autoreconf to bring 'configure' up-to-date
scripts Tile64 support added
test Use autoreconf to bring 'configure' up-to-date
.cvsignore ignore cscope database
.gitignore Fix .gitignore not to show generated files
ABOUT-NLS Updated to gettext 0.14.1
AUTHORS 2005-10-25 Jim Huang <>
ChangeLog Partial work for arm/jit3/NetBSD. (At least HelloWorldApp works)
ChangeLog.1 2003-08-10 Jim Pick <>
ChangeLog.10 Split the file up; it was getting rather large, and slow to checkin.
ChangeLog.11 Split the file up; it was getting rather large, and slow to checkin.
ChangeLog.12 Split the file up; it was getting rather large, and slow to checkin.
ChangeLog.13 Split the file up; it was getting rather large, and slow to checkin.
ChangeLog.14 Split the file up; it was getting rather large, and slow to checkin.
ChangeLog.15 Split ChangeLog again
ChangeLog.16 Rotated ChangeLog
ChangeLog.17 Rotated ChangeLog & enabled debugging on jit/powerpc.
ChangeLog.18 shuffled ChangeLogs
ChangeLog.19 2007-09-30 Dalibor Topic <>
ChangeLog.2 rotated changelogs
ChangeLog.20 moved 1.1.9 changelog over to ChangeLog.20
ChangeLog.3 * Updated changelogs.
ChangeLog.4 2002-11-23 Dalibor Topic <>
ChangeLog.5 2003-06-12 Dalibor Topic <>
ChangeLog.6 Moved old ChangeLog info into its own file
ChangeLog.7 Moved old ChangeLog info into its own file
ChangeLog.8 Moved old ChangeLog info into its own file
ChangeLog.9 Shuffled changelogs
INSTALL Some misc wording tweaks, etc. removed old kaffe awt implementations Use autoreconf to bring 'configure' up-to-date
README Minor grammar correction in README.
RELEASE-NOTES updated version to 1.1.10-pre
THIRDPARTY updated THIRDPARTY licensing information
TODO documented old AWT purge
WHATSNEW documented old AWT purge
aclocal.m4 Use autoreconf to bring 'configure' up-to-date added configuration files for test-autobuild
configure Fix ltdl.h auto-detection Fix ltdl.h auto-detection
license-lesser.terms Updated FSFs address all over the place
license.terms Updated FSFs address all over the place Add new docbook docs. Add new docbook docs.



			   Kaffe 1.1.10-pre


This is "Kaffe", a virtual machine which allows the execution of 
Java code.

Why use Kaffe?

Because Kaffe is distributed under the terms of the GNU Public License
which means the source code is free for you to download, modify and

What systems does Kaffe support?

Most of the porting issues of Kaffe are in the virtual machine itself
(after all, the rest is in Java and is therefore inherently portable)
so we may not support all the platforms you might want, but we support
an amazing number and we'll add more as we can.  Take a look at the list
below to see if Kaffe will run on your system ('J' means 'just-in-time'
while 'I' means 'interpreter'):

  uProc     | Mode |    Systems
  Alpha     | J+I  |    Linux		OSF/1		NetBSD 1.x
            |      |    FreeBSD
  ARM       | J+I  |    Linux           NetBSD 1.x	RISC OS
  Blackfin  | J+I  |    uclinux
  ia64	    | I	   |	Linux 2.x	HPUX 11.x       FreeBSD
  i386      | J+I  |    Linux 2.x       FreeBSD 2.x +   NetBSD 1.x
            |      |    Solaris 2.x     BSDI 2.x        Unixware
            |      |    SCO 3.2v5       NeXTStep 3.x    Windows '95/98/NT
            |      |    DG/UX		OpenBSD 2.x	OpenStep 4.x
            |      |    QNX 4.x		NCR MP-RAS 3.x  OSKit 0.96 +
            |      |    GNU Hurd	BeOS		Cygwin
	    |      |    Darwin          DragonFly BSD   Interix
  MIPS      | J+I  |    Linux           IRIX 5 & 6	NetBSD 1.x
	    |	   |	Ultrix 4.2      PS2Linux
  M68K      | J+I  |    AmigaOS         NeXTStep 3.x    NetBSD 1.x
            |      |    SunOS 4.x	Linux		AUX
            |      |    OpenBSD 2.x
  PARISC    | I    |    HPUX 10.x       Linux 2.x
  PowerPC   | I    |    Linux 2.x       MachTen 4.0.3	AIX
	    |	   |	Darwin		NetBSD1.x       Mac OS X
            |      |    OpenBSD
  s390	    | I	   |	Linux 2.x
  Sparc     | J+I  |    Linux 2.x       SunOS 4.x       NetBSD 1.x
            |      |    NeXTStep 3.x    Solaris 2.x	Fujitsu UXP/DS
            |      |    BSDI 3.x	OpenBSD 2.x
  SuperH    | I    |    Linux 2.x
  x86-64    | I    |    Linux 2.x	FreeBSD 2.x +   OpenBSD 4.x

Who can use Kaffe?

Kaffe is distributed under the GPL (GNU Public License).  Please
read the license to make sure it's okay to use it in your circumstances.

Where do I find new copies of Kaffe?

Kaffe is available from various sites.  The primary site is:

What about a web site?

News about the "Open Source" Kaffe distribution can always be found at:

And mailing lists?

There is a Google group available at:

Historic mailing list archives for the old kaffe mailing lists are here:

How do I report bugs and problems?

You can use GitHub issues here.

Note that the project is currently dormant, and not under active development. So
you might want to raise the issue in the Google Group as well in order to raise
awareness of your problem. New developers and pull requests are welcome!

What software do I need to install Kaffe?

See FAQ/FAQ.requiredlibraries.

You'll also need a compiler for the Java programming language, like ecj, 
javac or jikes. 

How do I compile and install kaffe?

For UNIX it couldn't be simpler:

  $ ./configure
  $ make
  $ make install

You can specify which compiler for the Java programming language to 
use for the build by passing it in the JAVAC variable to the configure 
script, as in

$ ./configure JAVAC=/usr/bin/ecj

Before compiling for your platform, you might want to check the
RELEASE-NOTES file to see if it has been tested with this release, and
whether or not there are any problems that other people have seen.

The virtual machine comes complete with the interpreter, stub generator,
and supporting native libraries.  Compilation is controlled using the
GNU autoconf program.  To generate the necessary makefiles
type "./configure" in this directory.  This will identify your system
and configure the software appropriately.  If JIT mode is supported on your
system it will be selected automatically, otherwise it defaults to
interpreting mode.  Compilation should then be a simple matter of
typing "make" in this directory.

Note: You will need GNU make ("gmake") in order to build Kaffe.

By default, the system will install into the /usr/local/kaffe
hierarchy in a layout similar to how Sun's JDK lays out the files,
with SDK tools (eg.  the java compiler) at the top level, and runtime
files only in the "jre" subdirectory).  The install location can be
changed using the --prefix option to configure.  To install the
binaries type "make install".

Kaffe can be reconfigured in a number of ways:

1. Use --program-prefix, --program-suffix or --program-transform-name
   configure option to prepend or append a string, or edit (with a sed
   command) all command names.
2. Use the --prefix configure option to place the kaffe installation tree
   somewhere other than /usr/local/kaffe.

For Windows 9x/NT, you can compile it using Red Hat's GNU tools for
Windows from:

Compilation and installation is as per the UNIX system.

Running Kaffe

No environment configuration is necessary to run kaffe.  However, you may 
want to include the directory in which kaffe is installed in your path.  
Typically, this would be /usr/local/kaffe/bin:


All necessary setup is taken care of by `kaffe' (note the lower case),
which is actually a driver shell script for the `kaffe-bin'

Note that you don't have to setup the CLASSPATH - if you do then that's
fine, but if you don't kaffe will construct a classpath that has the
current directory plus the Jar and Zip files it needs to run.  For the 
details of how the CLASSPATH is set up, refer to kaffe/scripts/

If you want to test the kaffe executable you built, type "make check".
This will run a suite of tests to check that your Kaffe executable is
in fact working.

The Kaffe Team

* is a an independent, free software community project, not
  directly affiliated with Transvirtual Technologies, Inc.
* The Kaffe virtual machine is free software, licensed under the terms
  of the GNU Public License.  It is a separate software product from
  Transvirtual's proprietary KaffePro virtual machine.
* Kaffe is a Trademark of Transvirtual Technologies, Inc.
* Java is a Trademark of Sun Microsystems, Inc.

Something went wrong with that request. Please try again.