This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
GCJ on mipsel-unknown-linux-gnu
- From: Andrew Haley <aph at redhat dot com>
- To: Casey Marshall <rsdio at metastatic dot org>
- Cc: java at gcc dot gnu dot org
- Date: Thu, 15 Apr 2004 18:25:16 +0100
- Subject: GCJ on mipsel-unknown-linux-gnu
- References: <87brlt6u6y.fsf@metastatic.org>
Casey Marshall writes:
> Hi. I'm currently trying to get gcj 3.3.3 up and working on
> mipsel-linux, and have gotten pretty far by patching the 3.3.3 release
> with the diffs listed here:
> <http://gcc.gnu.org/ml/gcc-cvs/2003-10/msg00902.html>
I don't think those patches were for 3.3; I thought they were for
mainline (now 3.5ish.)
> But I've caught a few snags. My first question is whether or not there
> are any other patches that I should try incorporating besides those in
> the above URL.
I think David was just about all finished with the MIPS stuff. I
remember someone (RTH, probably) suggesting a small change to his
MD_FALLBACK_FRAME_STAT_FOR, but that was it.
> The first obvious problem I have is that stack traces aren't pretty;
> they are composed of just addresses and "Unknown Source". I understand
> that libgcj will try to use dladdr to resolve the function names, but
> that dladdr doesn't work on mips (and indeed, if I remove the
> `disable_dladdr' line in configure.host, dladdr (or something called
> by it) hits a SEGV). The `c++filt'/`addr2line' hack doesn't work,
> because addr2line 2.14 can't seem to resolve function names in shared
> libraries (I am pretty much forced to use dynamic linking right now,
> since just about everything I am trying to run needs to load classes
> dynamically).
Ouch.
>
> GNU Awk 3.1.3 seems to really dislike `addr2name.awk'. It fails with
> this:
>
> sh: -c: line 1: syntax error near unexpected token `|'
> sh: -c: line 1: ` | sort'
>
> which looks like a newline is being inserted at the end of ARGV[1]:
>
> object = ARGV[1];
> ...
> while ("nm " object "| sort" | getline) {
Ouch. That is standard Awk, AFAIK. It must be a bug.
> I also see that --enable-interpreter doesn't work. Is this an issue
> with libffi?
Yes.
Andrew.