public inbox for
 help / color / mirror / Atom feed
From: Stefan Seefeld <>
Subject: rhug and gcc 3.3
Date: Thu, 15 May 2003 05:11:00 -0000	[thread overview]
Message-ID: <> (raw)

hi there,

I'm trying to build rhug with today's release
of gcc 3.3, with mixed success.

I'v close to no experience with gcj, and only
very limitted exposure to java, so please bear
with me.

One thing I noted is that the construct

(cd upstream/src; for x in `find ./ -name \*.class`; do $(GCJH) `echo $$x | sed "s/\.\///g" | sed 
"s/.class//g"`; done;)

that is being used in quite a number (if not all) Makefiles,
often fails with an error message indicating that the respective
class couldn't be found. Inserting a simple '--classpath=.' solves

Further, I list some package-specific errors:

jython: compile error

make[1]: Entering directory `/home/stefan/rhug/jython'
here=`pwd`; cd ./upstream/src/Lib; gcj -I.. -d $here/upstream/src/Lib -C -fno-assert 
--encoding=8859_1 jxxload_help/
jxxload_help/ error: Type `JavaLoaderFactory' not found in declaration of 
field `factory'.
        private JavaLoaderFactory factory;
jxxload_help/ error: Type `JavaLoaderFactory' not found in the declaration of 
the argument `factory' of method `<init>'.
        public PackageManager(org.python.core.PyList path,JavaLoaderFactory factory) {
2 errors

jakarta-tomcat: link error
========================== undefined reference to `org::apache::xml::serialize::DOMWriterImpl::class$'

jakarta-log4j: link error

Finally, I ran 'make clean' in xerces, when I discovered
that some errors got ignored (possibly leading to the
missing symbols above), and ran 'make' again, this time
with a fixed Makefile (added classpath...).
This time the link failed due to a libtool error, i.e.
some .lo files weren't found. No idea why they were
generated the first time.

Anyways, I'm looking forward to be able to use all your nice
work. My goal is to get jacORB compiled and running with gcj,
so I can write CORBA clients using jacORB for my own project

Kind regards,

             reply	other threads:[~2003-05-15  5:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15  5:11 Stefan Seefeld [this message]
2003-05-15  8:57 ` Gary Benson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).