strange java/jdk16 build error while building over tmpfs

[Dmitry Morozovsky]

On Mon, 18 Oct 2010, Dmitry Morozovsky wrote:

DM> KB> > I use ports tinderbox with working place null-m,ounted over tmpfs. Quite a few 
DM> KB> > ports are failing to build in such situation, such as jdk16. End of build log 
DM> KB> > (regardless of 7/8, i386/amd64) is
DM> KB> > 
DM> KB> > gmake[4]: Entering directory 
DM> KB> > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
DM> KB> > /usr/local/diablo-jdk1.6.0/bin/javap javax.xml.transform.TransformerFactory > 
DM> KB> > /dev/null 2>&1; \
DM> KB> > 	if [ $? -ne 0 ]; then \
DM> KB> > 	  /usr/local/diablo-jdk1.6.0/bin/java -version; \
DM> KB> > 	  echo "*** An XSLT processor (J2SE 1.4.x or newer) is required" \
DM> KB> > 	  "to bootstrap this build" 1>&2; \
DM> KB> > 	  exit 1; \
DM> KB> > 	fi
DM> KB> > Error: could not find libjava.so
DM> KB> > Error: could not find Java 2 Runtime Environment.
DM> KB> > *** An XSLT processor (J2SE 1.4.x or newer) is required to bootstrap this build
DM> KB> > gmake[4]: *** [check_j2se_version] Error 1
DM> KB> > gmake[4]: Leaving directory 
DM> KB> > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
DM> KB> > gmake[3]: *** [bsd_amd64_compiler2/debug] Error 2
DM> KB> > gmake[3]: Leaving directory 
DM> KB> > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
DM> KB> > gmake[2]: *** [generic_build2] Error 2
DM> KB> > gmake[2]: Leaving directory `/work/a/ports/java/jdk16/work/hotspot/make'
DM> KB> > gmake[1]: *** [product] Error 2
DM> KB> > gmake[1]: Leaving directory `/work/a/ports/java/jdk16/work/hotspot/make'
DM> KB> > gmake: *** [hotspot-build] Error 2
DM> KB> > *** Error code 2
DM> KB> > 
DM> KB> > Stop in /a/ports/java/jdk16.
DM> KB> > 
DM> KB> > 
DM> KB> > Any hints? Thanks!
DM> KB> > 
DM> KB> > Please keep me in CC: as I'm not subscribed to -java@ list.
DM> KB> 
DM> KB> Do you have procfs mounted in the build jail/chroot ? If yes, the issue
DM> KB> is known. vn_fullpath(9) has some issues resolving the vnode to the cached
DM> KB> path over nullfs. As a consequence, /proc/pid/file symlink sometimes cannot
DM> KB> be resolved, and AFAIK jdk uses it to find the base of installation.
DM> 
DM> Yes, ports tinderbox mounts procfs and linprocfs under buildarea; I'm afraid 
DM> it's rather hard to avoid.
DM> 
DM> KB> I tried to fix the problem in r193175, and it works for me. You should
DM> KB> supply some useful diagnostic to move the issue forward.
DM> 
DM> I'll try this and report back.

I've merged r193175 (null_vptocnp), but unfortunately it does not help: the 
error is precisely the same.

-- 
Sincerely,
D.Marck                                     [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer:                                 marck at FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
------------------------------------------------------------------------