strange java/jdk16 build error while building over tmpfs

[Dmitry Morozovsky]

On Sun, 17 Oct 2010, Kostik Belousov wrote:

KB> On Sun, Oct 17, 2010 at 12:35:37PM +0400, Dmitry Morozovsky wrote:
KB> > Dear colleagues,
KB> > 
KB> > I use ports tinderbox with working place null-m,ounted over tmpfs. Quite a few 
KB> > ports are failing to build in such situation, such as jdk16. End of build log 
KB> > (regardless of 7/8, i386/amd64) is
KB> > 
KB> > gmake[4]: Entering directory 
KB> > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
KB> > /usr/local/diablo-jdk1.6.0/bin/javap javax.xml.transform.TransformerFactory > 
KB> > /dev/null 2>&1; \
KB> > 	if [ $? -ne 0 ]; then \
KB> > 	  /usr/local/diablo-jdk1.6.0/bin/java -version; \
KB> > 	  echo "*** An XSLT processor (J2SE 1.4.x or newer) is required" \
KB> > 	  "to bootstrap this build" 1>&2; \
KB> > 	  exit 1; \
KB> > 	fi
KB> > Error: could not find libjava.so
KB> > Error: could not find Java 2 Runtime Environment.
KB> > *** An XSLT processor (J2SE 1.4.x or newer) is required to bootstrap this build
KB> > gmake[4]: *** [check_j2se_version] Error 1
KB> > gmake[4]: Leaving directory 
KB> > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
KB> > gmake[3]: *** [bsd_amd64_compiler2/debug] Error 2
KB> > gmake[3]: Leaving directory 
KB> > `/work/a/ports/java/jdk16/work/control/build/bsd-amd64/hotspot/outputdir'
KB> > gmake[2]: *** [generic_build2] Error 2
KB> > gmake[2]: Leaving directory `/work/a/ports/java/jdk16/work/hotspot/make'
KB> > gmake[1]: *** [product] Error 2
KB> > gmake[1]: Leaving directory `/work/a/ports/java/jdk16/work/hotspot/make'
KB> > gmake: *** [hotspot-build] Error 2
KB> > *** Error code 2
KB> > 
KB> > Stop in /a/ports/java/jdk16.
KB> > 
KB> > 
KB> > Any hints? Thanks!
KB> > 
KB> > Please keep me in CC: as I'm not subscribed to -java@ list.
KB> 
KB> Do you have procfs mounted in the build jail/chroot ? If yes, the issue
KB> is known. vn_fullpath(9) has some issues resolving the vnode to the cached
KB> path over nullfs. As a consequence, /proc/pid/file symlink sometimes cannot
KB> be resolved, and AFAIK jdk uses it to find the base of installation.

Yes, ports tinderbox mounts procfs and linprocfs under buildarea; I'm afraid 
it's rather hard to avoid.

KB> I tried to fix the problem in r193175, and it works for me. You should
KB> supply some useful diagnostic to move the issue forward.

I'll try this and report back.

Thank you!


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