This is the mail archive of the
java-discuss@sourceware.cygnus.com
mailing list for the Java project.
Re: installation name for gc library
- To: Matthias Klose <doko@cs.tu-berlin.de>
- Subject: Re: installation name for gc library
- From: Tom Tromey <tromey@cygnus.com>
- Date: Sun, 22 Aug 1999 10:00:35 -0700
- Cc: java-discuss@sourceware.cygnus.com
- References: <14271.56552.803323.350905@bolero>
Matthias> Currently the gc library is installed under the name
Matthias> libgcjgc. Assuming that libgcj is beeing integrated in gcc
Matthias> (?), ObjC could use this library as well, when configured
Matthias> with --enable-objc-gc. Is the libgcjgc already too gcj
Matthias> specific and cannot be used for ObjC? If not, could the
Matthias> library renamed to something less gcj specific, like
Matthias> libgccgc (where gcc now stands for compiler collection).
I think we would like to integrate libgcj into the gcc tree, but I
don't know when that will happen. We haven't yet re-entered
discussion with the egcs maintainers about it. Last time it was
derailed by licensing problems, but I think we've addressed those.
We don't have any major changes to the GC library in our tree. We
have some that look major, but they aren't: either they were sent to
Boehm for inclusion in a later version, or they were ported back to
our tree from a later version.
The real problem is that the Boehm GC is mostly only build-time
configurable. For instance, you must select Java finalization
semantics at build time, not run time. Boehm knows about this and (I
believe) is working on it.
Once this is sovled we can do what we do for zlib: if there is a
system zlib, use it, otherwise use ours (with a name change just in
case).
Once libgcj is in the gcc tree, I think we should revisit the
configure option names (--enable-objc-gc might override --enable-gc,
but shouldn't be the only option), as well as the GC library name.
Tom