strange java/jdk16 build error while building over tmpfs

[Kostik Belousov]

On Sun, Oct 17, 2010 at 12:35:37PM +0400, Dmitry Morozovsky wrote:
> Dear colleagues,
> 
> I use ports tinderbox with working place null-m,ounted over tmpfs. Quite a few 
> ports are failing to build in such situation, such as jdk16. End of build log 
> (regardless of 7/8, i386/amd64) is
> 
> gmake[4]: Entering directory 
> `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
> /usr/local/diablo-jdk1.6.0/bin/javap javax.xml.transform.TransformerFactory > 
> /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 
> `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
> gmake[3]: *** [bsd_amd64_compiler2/debug] Error 2
> gmake[3]: Leaving directory 
> `/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
> 
> Stop in /a/ports/java/jdk16.
> 
> 
> Any hints? Thanks!
> 
> 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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-java/attachments/20101017/c5163cfd/attachment.pgp