From: Elizabeth Barham <soggytrousers@yahoo.com>
To: <rhug-rhats@sources.redhat.com>
Subject: Re: Should xerces build out of the box?
Date: Tue, 23 Oct 2001 17:50:00 -0000 [thread overview]
Message-ID: <87d73dc19o.fsf@liliwhite.open.oasis> (raw)
Hi Tom,
Tom Tromey <tromey@redhat.com> writes:
> Cool!
:-)
> What version of gcj are you using?
Reading specs from /usr/lib/gcc-lib/powerpc-linux/2.95.4/specs
gcc version 2.95.4 20011006 (Debian prerelease)
Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.0.2/specs
Reading specs from /usr/lib/gcc-lib/powerpc-linux/3.0.2/../../../libgcj.spec
rename spec lib to liborig
rename spec startfile to startfileorig
Configured with: ../src/configure -v --enable-languages=c,c++,java,f77,proto,objc --prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --disable-checking --enable-threads=posix --enable-java-gc=boehm --with-cpp-install-dir=bin --enable-objc-gc powerpc-linux
Thread model: posix
gcc version 3.0.2 20011014 (Debian prerelease)
> 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.
That must be the problem then. I'll look into updating.
Thank you,
Elizabeth
next reply other threads:[~2001-10-23 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 17:50 Elizabeth Barham [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 17:32 Elizabeth Barham
2001-10-23 17:39 ` Tom Tromey
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=87d73dc19o.fsf@liliwhite.open.oasis \
--to=soggytrousers@yahoo.com \
--cc=rhug-rhats@sources.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).