Date: Tue, 26 May 2009 15:12:08 -0400 From: Todd Wasson <tsw5@duke.edu> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-stable@freebsd.org Subject: Re: jdk15/jdk16 build problems on amd64, 7.2-RELEASE Message-ID: <4A1C3F08.90809@duke.edu> In-Reply-To: <20090526183832.GN52703@dan.emsphone.com> References: <D2709B3A-D4EF-4398-985E-9091ABC148B1@duke.edu> <20090526183832.GN52703@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm... Well, this machine has 6GB of memory. I just killed firefox and other processes requiring significant memory and tried again, watching top. It didn't drop below 2GB inactive memory, and the 4GB of swap wasn't touched, so I kind of doubt that's the problem. For kicks, I'll try rebooting the machine and building again, just in case something funny is going on. Todd Dan Nelson wrote: > In the last episode (May 26), Todd Wasson said: >> I've recently been unable to get jdk15 and jdk16 to build, with some >> very cryptic errors (if any, really) being reported. I've pasted a >> build log for jdk16 here, since it's about 9100 lines long: http://paste2.org/p/224897 >> >> This seems to be the relevant portion: >> cd bsd_amd64_compiler2/product && gmake -w >> gmake[4]: Entering directory `/usr/ports/java/jdk16/work/control/build/ >> bsd-amd64/hotspot/outputdir/bsd_amd64_compiler2/product' >> Note: Some input files use unchecked or unsafe operations. >> Note: Recompile with -Xlint:unchecked for details. >> gmake[4]: *** [../generated/MakeDeps.class] Killed: 9 > > Something sent a KILL signal to your process. Maybe you ran out of memory > and the kernel killed the largest process it saw? >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A1C3F08.90809>