This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Java Patches: -fno-org-xml-sax and -fno-org-w3c-dom
- From: Anthony Green <green at redhat dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: java-patches at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: 22 Dec 2002 08:48:36 -0800
- Subject: Re: Java Patches: -fno-org-xml-sax and -fno-org-w3c-dom
- References: <1038718968.31616.23.camel@escape> <87k7i4mjhw.fsf@fleche.redhat.com>
On Fri, 2002-12-20 at 14:08, Tom Tromey wrote:
> If you want to, feel free to check in the libgcj part. If you do
> that, please update the manual to reflect the need for the new `-l'
> options.
Done.. to both branch and trunk. Thanks.
2002-12-22 Anthony Green <green@redhat.com>
* gcj.texi (Limitations): Add note about org.xml.sax and
org.w3c.dom.
Index: gcj.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/java/gcj.texi,v
retrieving revision 1.43
diff -2 -c -p -r1.43 gcj.texi
*** gcj.texi 16 Dec 2002 21:59:43 -0000 1.43
--- gcj.texi 22 Dec 2002 16:43:39 -0000
*************** from the JDK implementation. This is no
*** 516,519 ****
--- 516,530 ----
affects you, it probably makes sense to report it so that we can discuss
the appropriate response.
+
+ @item
+ @command{gcj} does not currently allow for piecemeal replacement of
+ components within @code{libgcj}. Unfortunately, programmers often want
+ to use newer versions of certain packages, such as those provided by
+ the Apache Software Foundation's Jakarta project. This has forced us
+ to place the @code{org.w3c.dom} and @code{org.xml.sax} packages into
+ their own libraries, separate from @code{libgcj}. If you intend to
+ use these classes, you must link them explicitly with
+ @code{-l-org-w3c-dom} and @code{-l-org-xml-sax}. Future versions of
+ @command{gcj} may not have this restriction.
@end itemize