head 1.8; access; symbols pkgsrc-2013Q2:1.8.0.24 pkgsrc-2013Q2-base:1.8 pkgsrc-2012Q4:1.8.0.22 pkgsrc-2012Q4-base:1.8 pkgsrc-2011Q4:1.8.0.20 pkgsrc-2011Q4-base:1.8 pkgsrc-2011Q2:1.8.0.18 pkgsrc-2011Q2-base:1.8 pkgsrc-2009Q4:1.8.0.16 pkgsrc-2009Q4-base:1.8 pkgsrc-2008Q4:1.8.0.14 pkgsrc-2008Q4-base:1.8 pkgsrc-2008Q3:1.8.0.12 pkgsrc-2008Q3-base:1.8 cube-native-xorg:1.8.0.10 cube-native-xorg-base:1.8 pkgsrc-2008Q2:1.8.0.8 pkgsrc-2008Q2-base:1.8 pkgsrc-2008Q1:1.8.0.6 pkgsrc-2008Q1-base:1.8 pkgsrc-2007Q4:1.8.0.4 pkgsrc-2007Q4-base:1.8 pkgsrc-2007Q3:1.8.0.2 pkgsrc-2007Q3-base:1.8 pkgsrc-2007Q2:1.7.0.26 pkgsrc-2007Q2-base:1.7 pkgsrc-2007Q1:1.7.0.24 pkgsrc-2007Q1-base:1.7 pkgsrc-2006Q4:1.7.0.22 pkgsrc-2006Q4-base:1.7 pkgsrc-2006Q3:1.7.0.20 pkgsrc-2006Q3-base:1.7 pkgsrc-2006Q2:1.7.0.18 pkgsrc-2006Q2-base:1.7 pkgsrc-2006Q1:1.7.0.16 pkgsrc-2006Q1-base:1.7 pkgsrc-2005Q4:1.7.0.14 pkgsrc-2005Q4-base:1.7 pkgsrc-2005Q3:1.7.0.12 pkgsrc-2005Q3-base:1.7 pkgsrc-2005Q2:1.7.0.10 pkgsrc-2005Q2-base:1.7 pkgsrc-2005Q1:1.7.0.8 pkgsrc-2005Q1-base:1.7 pkgsrc-2004Q4:1.7.0.6 pkgsrc-2004Q4-base:1.7 pkgsrc-2004Q3:1.7.0.4 pkgsrc-2004Q3-base:1.7 pkgsrc-2004Q2:1.7.0.2 pkgsrc-2004Q2-base:1.7 pkgsrc-2004Q1:1.5.0.2 pkgsrc-2004Q1-base:1.5 pkgsrc-2003Q4:1.3.0.2 pkgsrc-2003Q4-base:1.3; locks; strict; comment @# @; 1.8 date 2007.08.22.14.49.22; author jlam; state dead; branches; next 1.7; 1.7 date 2004.05.22.21.32.34; author jmmv; state Exp; branches; next 1.6; 1.6 date 2004.04.02.10.12.33; author jmmv; state Exp; branches; next 1.5; 1.5 date 2004.02.28.00.49.03; author lukem; state Exp; branches; next 1.4; 1.4 date 2004.02.06.01.31.05; author jmc; state Exp; branches; next 1.3; 1.3 date 2003.08.13.15.22.14; author jschauma; state Exp; branches; next 1.2; 1.2 date 2003.08.11.01.25.48; author grant; state Exp; branches; next 1.1; 1.1 date 2003.08.11.01.24.11; author grant; state Exp; branches; next ; desc @@ 1.8 log @Don't bother stating that we need COMPAT_LINUX, as the packages we depend upon to supply the Linux shared libraries already tell the user this. The JDK packages also depend on the corresponding JRE package, so they don't need to show the same message -- keep the message with the JRE packages instead. @ text @=========================================================================== $NetBSD: MESSAGE.NetBSD,v 1.7 2004/05/22 21:32:34 jmmv Exp $ In order to be able to run the JVM, you will need to compile your kernel with the following options: options COMPAT_LINUX Then, you need to add the following line to your /etc/fstab: procfs /emul/linux/proc procfs rw,linux Furthermore, the maximum data segment size assigned to your user must be at least 262144. You may want to read ${JAVA_HOME}/README for details about running this JDK. =========================================================================== @ 1.7 log @Convert sun-{jre,jdk}14 to use java-env.mk. This implies that the packages now install several wrappers under ${PREFIX}/bin to run the binaries installed under ${JAVA_HOME}/bin easily. While here, drop the direct modification of PREFIX. Bump PKGREVISION to 1. @ text @d2 1 a2 1 $NetBSD: MESSAGE.NetBSD,v 1.6 2004/04/02 10:12:33 jmmv Exp $ @ 1.6 log @As this needs a procfs mounted with the linux option, suggest /emul/linux/proc as the mount point, instead of /proc. This way, one can mount a regular (i.e, w/o linux compatiblity) procfs under /proc. @ text @d2 1 a2 1 $NetBSD: MESSAGE.NetBSD,v 1.5 2004/02/28 00:49:03 lukem Exp $ d13 2 a14 3 Furthermore, the data segment size set by your shell's 'ulimit' builtin must be at least 262144 -- please refer to your shell's manual page for details. d18 1 a18 1 ${PREFIX}/README d20 1 a20 5 for details about running this JDK. In a nutshell you may want to set the following in your shell environment: JAVA_HOME to ${PREFIX} PATH to include ${PREFIX}/bin @ 1.5 log @sync to ../sun-jre14/MESSAGE.NetBSD rev 1.5: A ulimit datasize of 131072 (128K) is too small; crank to 262144 (256K). (Whilst 132096 (129K) does work for simple tests, it's better to be conservative and suggest something that should work most of the time...) @ text @d2 1 a2 1 $NetBSD: MESSAGE.NetBSD,v 1.5 2004/02/28 00:44:34 lukem Exp $ d11 1 a11 1 procfs /proc procfs rw,linux @ 1.4 log @Take out the CLASSPATH suggestion as it's 1. plain wrong (setting it to that will just cause compiles to explode in interesting ways as that's source, not .class files) 2. Not needed as it can infer the default CLASSPATH from JAVA_HOME @ text @d2 1 a2 1 $NetBSD: MESSAGE.NetBSD,v 1.3 2003/08/13 15:22:14 jschauma Exp $ d7 1 a7 1 options COMPAT_LINUX d14 1 a14 1 must be at least 131204 -- please refer to your shell's manual page for @ 1.3 log @Note that one needs procfs mounted with the 'linux' option, too. @ text @d2 1 a2 1 $NetBSD: MESSAGE.NetBSD,v 1.2 2003/08/11 01:25:48 grant Exp $ a23 1 CLASSPATH to ${PREFIX}/src.zip:. @ 1.2 log @wrap lines to <= 75 @ text @d2 1 a2 1 $NetBSD: MESSAGE.NetBSD,v 1.1 2003/08/11 01:24:11 grant Exp $ a6 2 makeoptions TEXTADDR=d0100000 options KERNBASE_LOCORE=0xd0000000 d9 3 a11 3 Your kernel needs to be build from current sources later than 2003-08-09. Otherwise, jdk will fail to run properly on programs that can throw NullPointerExceptions. @ 1.1 log @this stuff is NetBSD-specific, and not needed on Linux, Solaris, or likely any other platform, so move it to the platform specific MESSAGE for NetBSD. @ text @d2 1 a2 1 $NetBSD: MESSAGE,v 1.8 2003/08/10 23:59:55 christos Exp $ d15 3 a17 2 Furthermore, the data segment size set by your shell's 'ulimit' builtin must be at least 131204 -- please refer to your shell's manual page for details. @