From: Elizabeth Clarke <eclarke@aminocom.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Java
Date: Mon, 05 Jun 2000 13:53:57 +0000 [thread overview]
Message-ID: <393BB0F5.415E62C8@aminocom.com> (raw)
In-Reply-To: 200006021710.NAA19138@hoover.gilbarco.com
"Banks, Kelly" wrote:
> I was hitting the exact same error & wound up tracking it into the
> libtermcap.2.0.8 that I was using... Mine went away when I used the termcap
> available from Mvista.
Hmmm, didn't make any difference. But then I dont understand what
difference it could make. AIUI anything compiled with egcs ie the JDK
binaries are incompatible with anything compiled with gcc - my
libraries, because egcs
referenced the symbol register_frame_info. I tried making a library with
just that symbol and pre-loading it, but still got the error:
/usr/jre118-v2/bin/ppc/green_threads/jre: error in loading shared
libraries: /usr/jre118-v2/lib/ppc/green_threads/libjava.so: symbol
__register_frame_info, version GLIBC_2.0 not defined in file libc.so.6
with link time reference
I think I'm going to have to investigate the JDK-1.2.2 and glibc-2.1.3
from
Franz Sirl's site, unless I'm missing something completely?...
(probably!)
Beth
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-05 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-02 17:10 Java Banks, Kelly
2000-06-05 13:53 ` Elizabeth Clarke [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-02 17:59 Java Elizabeth Clarke
2000-06-02 17:08 ` Java Grant Erickson
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=393BB0F5.415E62C8@aminocom.com \
--to=eclarke@aminocom.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).