From: Anthony Green <green@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Java Patches: -fno-org-xml-sax and -fno-org-w3c-dom
Date: Sun, 22 Dec 2002 08:47:00 -0000 [thread overview]
Message-ID: <1040575723.1466.753.camel@escape> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2002-12-22 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1038718968.31616.23.camel@escape>
2002-12-01 9:55 ` Jeff Sturm
2002-12-01 10:21 ` Anthony Green
2002-12-01 15:07 ` Jeff Sturm
2002-12-01 10:17 ` Per Bothner
2002-12-01 10:29 ` Anthony Green
2002-12-01 11:04 ` Per Bothner
2002-12-20 14:07 ` Tom Tromey
2002-12-22 8:47 ` Anthony Green [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1040575723.1466.753.camel@escape \
--to=green@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).