From: Tom Tromey <tromey@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: more bugs
Date: Wed, 18 Dec 2002 16:41:00 -0000 [thread overview]
Message-ID: <87wum6zvoq.fsf@fleche.redhat.com> (raw)
I got BCEL to build by changing the top-level build order.
Also I had to change the top-level configure to know that
jakarta-regexp now has its own configure script.
Now I get the appended.
There doesn't appear to be a `de' directory anywhere in rhug.
I'm hoping someone out there can volunteer to make rhug build cleanly
with the latest cvs gcj. The gcj 3.3 release is coming up, and
unfortunately at this point it looks like I'll barely be able to keep
up with it -- I probably won't have time to fix the rhug problems I
keep hitting. I'd really like to have building rhug be a release
requirement for gcj, but I can only do that if rhug is in fact
buildable...
Tom
Making all in xalan
make[1]: Entering directory `/home/tromey/gnu/rhug/build/xalan'
gcj -C --encoding=8859_1 --classpath=upstream/src:../../rhug/xalan/../xerces/upstream/src:../../rhug/xalan/../BCEL/upstream:../../rhug/xalan/../cup/upstream:../../rhug/xalan/../gnu.regexp/upstream/src:../../rhug/xalan/upstream/src -O2 -d upstream/src ../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/cmdline/Compile.java
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/Constants.java:66: error: Class or interface `de.fub.bytecode.generic.InstructionConstants' not found in import.
import de.fub.bytecode.generic.InstructionConstants;
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/Constants.java:68: error: Superinterface `InstructionConstants' of interface `org.apache.xalan.xsltc.compiler.Constants' not found.
public interface Constants extends InstructionConstants {
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/XSLTC.java:89: error: Class or interface `de.fub.bytecode.classfile.JavaClass' not found in import.
import de.fub.bytecode.classfile.JavaClass;
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/FlowList.java:76: error: Type `InstructionHandle' not found in the declaration of the argument `bh' of method `<init>'.
public FlowList(InstructionHandle bh) {
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/FlowList.java:85: error: Type `InstructionHandle' not found in the declaration of the argument `bh' of method `add'.
public FlowList add(InstructionHandle bh) {
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/FlowList.java:112: error: Type `InstructionHandle' not found in the declaration of the argument `target' of method `backPatch'.
public void backPatch(InstructionHandle target) {
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/FlowList.java:116: error: Type `BranchHandle' not found in the declaration of the local variable `bh'.
BranchHandle bh = (BranchHandle)_elements.elementAt(i);
^
../../rhug/xalan/upstream/src/org/apache/xalan/xsltc/compiler/util/Type.java:290: confused by earlier errors, bailing out
make[1]: *** [upstream/src/org/apache/xalan/xsltc/cmdline/Compile.class] Error 1
make[1]: Leaving directory `/home/tromey/gnu/rhug/build/xalan'
make: *** [all-recursive] Error 1
next reply other threads:[~2002-12-19 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 16:41 Tom Tromey [this message]
2002-12-18 17:18 ` Anthony Green
2002-12-18 17:23 ` Tom Tromey
2002-12-18 18:28 ` Anthony Green
2002-12-18 17:52 ` Dhek Bhun Kho
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=87wum6zvoq.fsf@fleche.redhat.com \
--to=tromey@redhat.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).