From: Tom Tromey <tromey@redhat.com>
To: Elizabeth Barham <soggytrousers@yahoo.com>
Cc: <rhug-rhats@sources.redhat.com>
Subject: Re: Should xerces build out of the box?
Date: Tue, 23 Oct 2001 17:39:00 -0000 [thread overview]
Message-ID: <87k7xl3lem.fsf@creche.redhat.com> (raw)
In-Reply-To: <87hespc23z.fsf_-_@liliwhite.open.oasis>
>>>>> "Elizabeth" == Elizabeth Barham <soggytrousers@yahoo.com> writes:
Elizabeth> I know very little of java or gcj but I find this project very
Elizabeth> exciting and hope to aid somehow.
Cool!
Elizabeth> Via the pserver I pulled down the rhug tree and tried to compile
Elizabeth> xerces and xalan - the two applications I am most intetested in
Elizabeth> using. I could not get xerces to compile.
What version of gcj are you using?
rhug requires the latest CVS trunk gcc -- what will eventually be
known as gcc 3.1. This is a pain, because it means you have to build
your own gcc. However, it is necessary for now. gcj and libgcj are
still changing quite rapidly. Older releases, even gcj 3.0, are
noticeably less capable.
Tom
next prev parent reply other threads:[~2001-10-23 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 17:32 Elizabeth Barham
2001-10-23 17:39 ` Tom Tromey [this message]
2001-10-23 17:50 Elizabeth Barham
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=87k7xl3lem.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
--cc=soggytrousers@yahoo.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).