[ANNOUNCE] Libgcj in gcc tree availability.

Alexandre Petit-Bianco apbianco@cygnus.com
Sat Dec 9 22:07:00 GMT 2000

The libgcj (libjava, libffi and boehm-gc) have been brought to the top
level of the gcc tree. Yesterday, fastjar was imported from
sourceforge ( http://fastjar.sourceforge.net/ ). I just checked in the
following patch:


You should update your entire gcc tree to see these four new
directories (but be aware that gcc didn't build at all for me 30
minutes ago on x86/linux.)

If you change your updated toplevel configure.in to remove the mention
of `target-libjava' in the first assignment of `noconfigdirs', you
should be able to build libgcj:

Index: configure.in
RCS file: /cvs/gcc/egcs/configure.in,v
retrieving revision 1.78
diff -u -p -r1.78 configure.in
--- configure.in        2000/12/09 21:08:13     1.78
+++ configure.in        2000/12/10 05:50:20
@@ -549,7 +549,7 @@ esac
 # target this usually means that a port of the program doesn't
 # exist yet.
 case "${host}" in

Remember that libgcj still doesn't build unless you configure your
tree with `--disable-new-gxx-abi' (this is the reason of the tweak in
configure.in, it should be resolved soon.) --enable-shared and
--enable-threads=posix are libgcj's preferred configure options. You
shouldn't disable java from the list of language you build.

Known to build platforms are: x86/debian, sparc/debian, ppc/LinuxPPC2000,
x86/RHL6.x, x86/RHL7, alpha/RHL6.2 and alpha/RHL7. Solaris doesn't
build at this time.

Java hackers: you should save your library patches, get rid of your
libgcj tree; and after update, use gcc as your working libgcj
tree. The /cvs/java repository is no longer where the active
development takes place. For more information on how you should now
use CVS, read:


To everyone involved in this part of the Great Java Migration: thanks
a bunch.
Happy hacking!


More information about the Java mailing list