Re: [gentoo-user] Java configuration is hosed

2008-07-22 Thread Rev. Ferris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I used one hour ago the java update guide wiki. It's worked! Luigi Alle martedì 22 luglio 2008, Dave Jones ha scritto: > Hi Kevin, > > Kevin O'Gorman wrote on 22/07/08 20:03: > > On Tue, Jul 22, 2008 at 10:34 AM, Dave Jones <[EMAIL PROTECTED]> wrote:

Re: [gentoo-user] Java configuration is hosed

2008-07-22 Thread Dave Jones
Hi Kevin, Kevin O'Gorman wrote on 22/07/08 20:03: On Tue, Jul 22, 2008 at 10:34 AM, Dave Jones <[EMAIL PROTECTED]> wrote: Kevin O'Gorman wrote on 22/07/08 18:51: I cannot emerge the latest xulrunner, but the root cause appears to be my Java configuration. I haven't touched it in ages, so I ha

Re: [gentoo-user] Java configuration is hosed

2008-07-22 Thread Kevin O'Gorman
On Tue, Jul 22, 2008 at 10:34 AM, Dave Jones <[EMAIL PROTECTED]> wrote: > Hi Kevin > > Kevin O'Gorman wrote on 22/07/08 18:51: >> >> I cannot emerge the latest xulrunner, but the root cause appears to be >> my Java configuration. I haven't touched it in ages, so I have no >> idea how this happened

Re: [gentoo-user] Java configuration is hosed

2008-07-22 Thread Dave Jones
Hi Kevin Kevin O'Gorman wrote on 22/07/08 18:51: I cannot emerge the latest xulrunner, but the root cause appears to be my Java configuration. I haven't touched it in ages, so I have no idea how this happened. The evidence: treat ~ # eselect java-vm list Available Java Virtual Machines: [1]

Re: [gentoo-user] Java configuration is hosed

2008-07-22 Thread Dale
Kevin O'Gorman wrote: I cannot emerge the latest xulrunner, but the root cause appears to be my Java configuration. I haven't touched it in ages, so I have no idea how this happened. The evidence: treat ~ # eselect java-vm list Available Java Virtual Machines: [1] sun-jdk-1.4 [2] sun-jd

[gentoo-user] Java configuration is hosed

2008-07-22 Thread Kevin O'Gorman
I cannot emerge the latest xulrunner, but the root cause appears to be my Java configuration. I haven't touched it in ages, so I have no idea how this happened. The evidence: treat ~ # eselect java-vm list Available Java Virtual Machines: [1] sun-jdk-1.4 [2] sun-jdk-1.6 system-vm treat ~