Inclusion of GNU jaxp in libgcj

Sun Feb 8 17:24:00 GMT 2004

On Sun, Feb 08, 2004 at 11:04:25AM -0500, Jeff Sturm wrote:
> On Sun, 8 Feb 2004, Michael Koch wrote:
> > Its no problem to put GNU JAXP into its own DSO.
>> Oh, okay, then I withdraw my objection.
>> However I'm still bothered by the huge size of libgcj and bootstrap times.
> I know it's already been discussed at length on this list, so forgive me
> for mentioning it, but here are the current sizes of various language
> runtimes currently shipped with GCC (i686):
>> 117421 libg2c.so
> 1216686 libgnat.a
> 9269164 libgcj.so
> 802483 libstdc++.so
>> Many users of GCC, myself included, routinely build libgcj only for the
> purpose of regression testing the frontend. Having to build all of
> javax.* etc. each time is an unnecessary burden.
>> I have an idea. What do you think about adding support GCC's toplevel
> makefile to checkout and build classpathx as a target directory, separate
> from libgcj? Then there would be no need to import classpathx sources
> into the GCC repository, yet it would be simple for those who need it to
> checkout and build with the rest of GCC.

Well, GNU JAXP is not only part of classpathx, its part of classpath
and SUN's JDK/JRE 1.4 SE too. Users expect it to be included in a software
that has the goal to be an alternative to SUNs JRE.
We had a discussion on irc lately about stuff depending on gcj/libgcj
and tromey pointed out that maintaining stuff outside of gcc source tree
creates more problems then it solves. Even the idea to put libgcj
outside of gcc again came up.
Personally I dont think putting anything outside of gcc tree is a good
thing. I will not vote against your idea because its a nice way to
include additionaly packages into libgcj easily.
Michael