From: Randolph Chung <randolph@tausq.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: nwoods29321@charter.net, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Problems with Web
Date: Tue, 1 Jun 2004 22:29:05 -0700 [thread overview]
Message-ID: <20040602052905.GP3517@tausq.org> (raw)
In-Reply-To: <200405312258.i4VMwFRM021111@hiauly1.hia.nrc.ca>
> > Awesome!
> > Any rough estimate when something will be submitted to debian?
gcc-3.3 in Debian already has the java patches, but it doesn't work
very well there (lots of test failures). Dave and I are still trying to
sort out what is wrong with signal frame unwinding/libjava with gcc-3.5
and 2.4/2.6 kernels....
sablevm is supported on hppa-linux in switched and direct-threaded mode.
There are some issues with the inlined engine that I haven't had time to
investigate and figure out yet. It works quite well otherwise and is
actively being worked on.
kaffe can probably be made to work, at least in interpreter mode,
without too much work. It used to work ~2 years ago, but has probably
bitrotted since then. If anyone is interested in working on this and
needs help, let me know.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-06-02 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040531225013.GD26348@colo.lackof.org>
2004-05-31 22:58 ` [parisc-linux] Problems with Web John David Anglin
2004-06-02 5:29 ` Randolph Chung [this message]
[not found] <20040531170503.GL16157@baldric.uwo.ca>
2004-05-31 17:43 ` John David Anglin
[not found] <20040529100944.3D6513BE2E@free.linux.hp.com>
2004-05-30 12:49 ` Nathaniel
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=20040602052905.GP3517@tausq.org \
--to=randolph@tausq.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=nwoods29321@charter.net \
--cc=parisc-linux@lists.parisc-linux.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