Date: Sun, 20 May 2012 11:21:31 -0700 From: Greg Lewis <glewis@eyesbeyond.com> To: Horst Leitenmueller <horst.leitenmueller@liwest.at> Cc: java@freebsd.org, glewis@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Procfs in Jail on fresh install of openjdk6 Message-ID: <20120520182131.GA10138@misty.eyesbeyond.com> In-Reply-To: <907F19BE-DB86-42A7-A153-60830A5CD5CC@liwest.at> References: <907F19BE-DB86-42A7-A153-60830A5CD5CC@liwest.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 18, 2012 at 09:22:31AM +0200, Horst Leitenmueller wrote: > hi Greg, > > i have a question regarding the hint that procfs must be enabled on openjdk6 > > if this is already mounted before installation of openjdk6 the build fails with: > > gmake[2]: Entering directory `/s/portbuild/usr/ports/java/openjdk6/work/langtools/make' > JAVA_HOME=/usr/local/diablo-jdk1.6.0 ANT_OPTS=-Djava.io.tmpdir='/s/portbuild/usr/ports/java/openjdk6/work/build/bsd-amd64/langtools/build/ant-tmp' /s/portbuild/usr/ports/java/openjdk6/work/apache-ant-1.8.2/bin/ant -Djdk.version=1.6.0_30 -Dfull.version='1.6.0_30-b24' -Drelease=1.6.0_30 -Dbuild.number=b24 -Djavac.target=5 -Dboot.java.home=/usr/local/diablo-jdk1.6.0 -Dbuild.dir=/s/portbuild/usr/ports/java/openjdk6/work/build/bsd-amd64/langtools/build -Ddist.dir=/s/portbuild/usr/ports/java/openjdk6/work/build/bsd-amd64/langtools/dist build > Error: could not find libjava.so > Error: could not find Java 2 Runtime Environment. > gmake[2]: *** [build] Error 2 > gmake[2]: Leaving directory `/s/portbuild/usr/ports/java/openjdk6/work/langtools/make' > gmake[1]: *** [langtools-build] Error 2 > gmake[1]: Leaving directory `/s/portbuild/usr/ports/java/openjdk6/work' > gmake: *** [build_product_image] Error 2 > *** Error code 1 > > Stop in /usr/ports/java/openjdk6. > *** Error code 1 > > > diablo-jdk1.6 is installed (with the openjdk port) but you can't call java --version (on commandline) for example > > can you please explain if this is a feature or a bug; and when the procfs must be enabled ? > > if i disable the procfs build is running through (java --version for diablo running normal, and also openjdk), > afterwards enabling does not change functionality of java, it works without problems... Based on the above, it's Diablo that is having problems with procfs being mounted. I have some recollection of changing around how we detected where the JDK really is installed when the java executable ran, one of the possible ways being procfs based. The version in Diablo seems to not cope with procfs correctly. Once OpenJDK6 is built there may well be some internal functionality that doesn't work based on procfs being mounted. I think there may be some code in the HotSpot Serviceability Agent that uses that, but it's been a while since I was looking at that. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120520182131.GA10138>