On Sunday 15 January 2006 18:35, Kurt Miller wrote: > On Sunday 15 January 2006 3:28 am, viq wrote: > > On Sunday 15 January 2006 05:20, Tobias Ulmer wrote: > > > On Sat, Jan 14, 2006 at 10:52:10PM -0500, Kurt Miller wrote: > > > > That should be enough memory for the build. > > > > > > > > I'm looking into a similar problem in 1.4 right now. The segfault > > > > is random and the few times I caught it in gdb, I didn't get a > > > > backtrace that led me to the problem. > > > > > > > > The breakage occured somewhere after the Dec 22 snapshot. > > > > > > I had that too and a ports tree update solved it for me. > > > see > > > http://www.openbsd.org/cgi-bin/cvsweb/ports/devel/jdk/1.4/Makefile > > > and > > > http://www.openbsd.org/cgi-bin/cvsweb/ports/devel/jdk/1.5/Makefile > > > > or rather > > http://www.openbsd.org/cgi-bin/cvsweb/ports/devel/jdk/1.5/patches/pat > >ch-j2se_src_share_bin_java_c as that is what was changed (for both 1.4 > > and 1.5) > > > > Which is present in my ports tree... > > I committed that to fix another problem.
Yeah. I posted that as reply to "The breakage occured somewhere after the Dec 22 snapshot." > The -current random segfault is > a different problem and has nothing to do with how much memory you have > or disk space available. Yes, apparently. Any idea what could this be? I'll run now several kernel builds on the linux host to verify the hardware is not causing problems. > -Kurt -- viq ---------------------------------------------------------------------- Kliknij po wiecej! >>> http://link.interia.pl/f18ed
