public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Oscar Martinez de la Torre <>
Cc: Java GCJ Mail List <>,
	Jiri Gaisler <>,
	Stig Mejnertsen <>
Subject: Re: Testing GCJ in Linux RedHat!
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

>>>>> "Oscar" == Oscar Martinez de la Torre <> writes:

Oscar> 	I'm trying to run JAVA in ERC32 (a space microprocessor like "sparc")
Oscar> 	I'm trying Kaffe + RTEMS (A RTOS which works on ERC32)
Oscar> 	But as I'm finding lots of problems in it (any suggestions is welcome)
Oscar> 	I'm also trying GCJ approach!

As far as I know libgcj has not been ported to RTEMS.

Oscar> /opt/rtems/bin/sparc-rtems-gcj

From the messages it looks like you don't have libgcj (of course), and
so you can't link.  libgcj is required to link a gcj-compiled program.

Oscar> 	Also, it seems that libgcj is no so easy to port and crosscompile!

I cross compile it routinely.
I've ported it, too.  It isn't trivial, but it is possible.
There is some help available on the web page.  Did you look there?

I doubt I'll be doing an RTEMS port unless somebody hires us to do
one.  We rely on volunteer effort for things like this.

Oscar> gcj  
Oscar> /usr/lib/crt1.o(.text+0x18): undefined reference to `main'
Oscar> /usr/lib/gcc-lib/i386-linux/2.95.2/ undefined reference to
Oscar> `__rethrow'
Oscar> /usr/lib/gcc-lib/i386-linux/2.95.2/ undefined reference to
Oscar> `__start_cp_handler'

Try gcj --main=HelloWorldApp

This is documented on our web pages:


  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-01  0:00 Oscar Martinez de la Torre
2000-04-01  0:00 ` Tom Tromey [this message]
     [not found]   ` <>
2000-04-01  0:00     ` Joel Sherrill
2000-04-01  0:00     ` 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:

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