JDK Issues

[Kent Stewart]

On Sunday 28 November 2004 02:20 pm, Lars Eighner wrote:
> On Sun, 28 Nov 2004, Jake Stride wrote:
> > I seem unable to install JDK14:
> >
> > portupgrade -NRP jdk
> > --->  Found 4 ports matching 'jdk':
> >        java/jdk11
> >        java/jdk12
> >        java/jdk13
> >        java/jdk14
> > Install 'java/jdk11'? [yes] no
> > Install 'java/jdk12'? [yes] no
> > Install 'java/jdk13'? [yes] no
> > Install 'java/jdk14'? [yes] yes
> > ** Port marked as IGNORE: java/jdk14:
> >        "is forbidden: Vulnerabilities in the browser plugin"
> >
> > How do I go about ensuring that I can install this please?
>
> If you can't figure this out for yourself, maybe you shouldn't
> be told.  Anyway, comment out the forbidden line in the Makefile.
>
> Well, that would work for most "forbidden" ports, but so far as
> I can tell, jdk14 won't build anyway.  After a very long compile
> it will come to a grinding halt with:
>
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack
> location
> /usr/local/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java/u
>til/Curren cyData.java:1:
> 'class' or 'in terface' expected
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack
> location ^
> /usr/local/ports/java/jdk14/work/control/build/bsd-i586/gensrc/java/u
>til/Curren cyData.java:1:
> unclosed chara cter literal
> Java HotSpot(TM) Client VM warning: Can't detect initial thread stack
> location ^
> 2 errors
> gmake[4]: *** [.compile.classlist] Error 1
> gmake[4]: Leaving directory
> `/usr/local/ports/java/jdk14/work/j2se/make/java/java'
> gmake[3]: *** [optimized] Error 2
> gmake[3]: Leaving directory
> `/usr/local/ports/java/jdk14/work/j2se/make/java/java'
> gmake[2]: *** [all] Error 1
> gmake[2]: Leaving directory
> `/usr/local/ports/java/jdk14/work/j2se/make/java' gmake[1]: *** [all]
> Error 1
> gmake[1]: Leaving directory
> `/usr/local/ports/java/jdk14/work/j2se/make' gmake: *** [j2se-build]
> Error 2
> *** Error code 2
>
> Stop in /usr/local/ports/java/jdk14.

There must be something missing on your system. It built just fine on 
mine. Of course, it just could be Murphy trying to confuse us :).

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html