All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: "marc. h." <heckmann@hbe.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: jdk 1.4?
Date: 28 Feb 2002 21:43:03 +0100	[thread overview]
Message-ID: <1014928983.828.2992.camel@tibook> (raw)
In-Reply-To: <20020228131151.GD2183@hbe.ca>


On Don, 2002-02-28 at 14:11, marc. h. wrote:
> On Tue, Feb 26, 2002 at 05:19:57PM +0100, Michel D?nzer wrote:
> > > > I hadn't actually tried the IBM JVM for PPC - the only link I'd seen for
> > > > it pointed to some SuSE site. I am, however, running 2.4.17-benh0 on
> > > > this iBook, so I guess if you experience is correct, it wouldn't work on
> > > > here anyhow. Also, did it come with an OJI Java plugin for use with
> > > > Mozilla? (I'd bet not.)
> > >
> > > Would you mind giving it a shot? (or someone else?) I want to be sure that it's
> > > not a local Glibc issue or such thing. I also haven't tried a recent benh
> > > kernel..
> >
> > Works here, but then I've applied a couple patches:
> > 2.4.18-pre9-benh-o1-xfs-lolat-aa ;)
> >
> > As you mention sched_yield(), the O(1) scheduler patch could make the
> > difference?
>
> hmm, I tried the O(1) scheduler with your patch and it still doesn't work.
>
> maybe it's lolat? or benh? I'll try that tonight.
>
> but could you do me a favour? can you try out 2.4.18-rc4 vanilla? and confirm
> that it doesn't work? that would eliminate the possiblity that it's a userspace
> issue (or rather some kind of kernel-userspace interaction problem)

Why don't you just try Debian instead? ;)

Seriously, I can't test vanilla because my filesystems are all XFS. :)
And it's not that I have too much time, if you know what I mean... I
hope you understand and that your own testing will give some results.


> and you're sure your trying the IBM-jdk right? could be that you have the
> blackdown JDK installed as well and it comes first in your PATH or something?

I do have the Blackdown 1.1 and 1.3 JDKs installed as well, but I used
the absolute path to the IBM java executable for testing. Coult it still
have picked up some wrong libraries or something?


--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-02-28 20:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-25 18:06 jdk 1.4? R Shapiro
2002-02-26  0:22 ` Josh Rosenau
2002-02-26  2:07   ` Michel Dänzer
2002-02-26  2:16   ` Steven Hanley
2002-02-26  4:03     ` Derrik Pates
2002-02-26 10:49       ` marc. h.
2002-02-26 16:00         ` Derrik Pates
2002-02-26 16:06           ` marc. h.
2002-02-26 16:19             ` Michel Dänzer
2002-02-28 13:11               ` marc. h.
2002-02-28 20:43                 ` Michel Dänzer [this message]
2002-03-01  6:26             ` Derrik Pates
2002-03-01 12:48               ` Marc Heckmann
2002-02-26 16:12           ` Ryan Boder
2002-02-28 13:28 ` Kevin B. Hendricks

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=1014928983.828.2992.camel@tibook \
    --to=michel@daenzer.net \
    --cc=heckmann@hbe.ca \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.