Hi
Thanks for all your support. As of the instructions given in http://ftp.netbsd.org:/pub/NetBSD/misc/spz/openjdk/openjdk7-howto <http://ftp.netbsd.org/pub/NetBSD/misc/spz/openjdk/openjdk7-howto> , I completed all the pre-install steps successfully. But as I gave gmake it exited with the following error: # # A fatal error has been detected by the Java Runtime Environment: # # Internal Error (nmethod.cpp:1836), pid=1012, tid=49190 # Error: guarantee(cont_offset != 0,"unhandled implicit exception in compiled code") # # JRE version: 6.0_14-b08 # Java VM: Java HotSpot(TM) Client VM (14.0-b16 mixed mode, sharing linux-x86 ) # An error report file with more information is saved as: # /teles/rema/jdk/bsd-port/langtools/make/hs_err_pid1012.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # I Installed "lang/sun-jdk6" from pkgsrc. And I'm working on a NetBSD 3.1 i386 machine... Regards, Renju -----Original Message----- From: S.P.Zeidler [mailto:s...@serpens.de] Sent: Friday, May 29, 2009 12:19 PM To: Renju Mathew Cc: bsd-port-dev@openjdk.java.net Subject: Re: netbsd port ? Hi, Thus wrote Renju Mathew (m.re...@teles.com): > I'm a newbie in openJDK. > > I want to know whether there is any NetBSD 3.0 port of openJDK? I built binaries for NetBSD 5.0 that are available via the openjdk-bin package in pkgsrc, but not for earlier releases (although I probably should build a NetBSD-4 version, since that's still an officially supported release train). I'd expect openjdk to just build on NetBSD-3, see http://ftp.netbsd.org:/pub/NetBSD/misc/spz/openjdk/openjdk7-howto for a recipy. Once you scrub your environment(*) it's fairly straightforward, it just takes a while to build. The patch I needed for the openjdk version I put onto ftp.NetBSD.org has since been integrated, so that one isn't necessary any more; but as lots of new code has been added, too, there's chance of entirely new fun to be had. :-P regards, spz (*) variables like eg $BIN get used as conditional, and the script that sets them as a "yes" indicator doesn't unset them as a "no" indicator, so if you already had them set because you use them differently, you get surprising results. If I had lots more time I'd want to hunt them all down. -- s...@serpens.de (S.P.Zeidler)
