From owner-freebsd-java@FreeBSD.ORG Sun Oct 17 13:57:19 2010 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69FFD1065675 for ; Sun, 17 Oct 2010 13:57:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id EF1B38FC12 for ; Sun, 17 Oct 2010 13:57:18 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o9HDjejk062672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 Oct 2010 16:45:40 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id o9HDjdIV038322; Sun, 17 Oct 2010 16:45:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o9HDjdKb038321; Sun, 17 Oct 2010 16:45:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 17 Oct 2010 16:45:39 +0300 From: Kostik Belousov To: Dmitry Morozovsky Message-ID: <20101017134539.GW2392@deviant.kiev.zoral.com.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UAAUMAtm6/xgGh2k" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-java@freebsd.org Subject: Re: strange java/jdk16 build error while building over tmpfs X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2010 13:57:19 -0000 --UAAUMAtm6/xgGh2k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 17, 2010 at 12:35:37PM +0400, Dmitry Morozovsky wrote: > Dear colleagues, >=20 > I use ports tinderbox with working place null-m,ounted over tmpfs. Quite = a few=20 > ports are failing to build in such situation, such as jdk16. End of build= log=20 > (regardless of 7/8, i386/amd64) is >=20 > gmake[4]: Entering directory=20 > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir' > /usr/local/diablo-jdk1.6.0/bin/javap javax.xml.transform.TransformerFacto= ry >=20 > /dev/null 2>&1; \ > if [ $? -ne 0 ]; then \ > /usr/local/diablo-jdk1.6.0/bin/java -version; \ > echo "*** An XSLT processor (J2SE 1.4.x or newer) is required" \ > "to bootstrap this build" 1>&2; \ > exit 1; \ > fi > Error: could not find libjava.so > Error: could not find Java 2 Runtime Environment. > *** An XSLT processor (J2SE 1.4.x or newer) is required to bootstrap this= build > gmake[4]: *** [check_j2se_version] Error 1 > gmake[4]: Leaving directory=20 > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir' > gmake[3]: *** [bsd_amd64_compiler2/debug] Error 2 > gmake[3]: Leaving directory=20 > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir' > gmake[2]: *** [generic_build2] Error 2 > gmake[2]: Leaving directory `/work/a/ports/java/jdk16/work/hotspot/make' > gmake[1]: *** [product] Error 2 > gmake[1]: Leaving directory `/work/a/ports/java/jdk16/work/hotspot/make' > gmake: *** [hotspot-build] Error 2 > *** Error code 2 >=20 > Stop in /a/ports/java/jdk16. >=20 >=20 > Any hints? Thanks! >=20 > Please keep me in CC: as I'm not subscribed to -java@ list. Do you have procfs mounted in the build jail/chroot ? If yes, the issue is known. vn_fullpath(9) has some issues resolving the vnode to the cached path over nullfs. As a consequence, /proc/pid/file symlink sometimes cannot be resolved, and AFAIK jdk uses it to find the base of installation. I tried to fix the problem in r193175, and it works for me. You should supply some useful diagnostic to move the issue forward. Try to unmount procfs from the build chroot as a workaround. --UAAUMAtm6/xgGh2k Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAky6/gIACgkQC3+MBN1Mb4jnOwCeOicsfOnassFspgoflKefVULC yIMAn0CJpLTTP1lpd0g/8KanBm6qsUxS =U8Ej -----END PGP SIGNATURE----- --UAAUMAtm6/xgGh2k--