From owner-freebsd-current@FreeBSD.ORG  Sat May 31 08:22:45 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id F149037B401; Sat, 31 May 2003 08:22:44 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1F32243F93; Sat, 31 May 2003 08:22:44 -0700 (PDT)
	(envelope-from eischen@pcnet.com)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h4VFMgNc008335;
	Sat, 31 May 2003 11:22:42 -0400 (EDT)
Date: Sat, 31 May 2003 11:22:42 -0400 (EDT)
From: Daniel Eischen <eischen@pcnet.com>
To: Dag-Erling Smorgrav <des@ofug.org>
In-Reply-To: <xzpsmqvladz.fsf@flood.ping.uio.no>
Message-ID: <Pine.GSO.4.10.10305311119460.7793-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: Norikatsu Shigemura <nork@freebsd.org>
Subject: Re: Native JDK with libthr/libkse
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 31 May 2003 15:22:45 -0000

On Sat, 31 May 2003, Dag-Erling Smorgrav wrote:

> Daniel Eischen <eischen@pcnet.com> writes:
> > What are the above error messages?  Sorry, I've never been able to
> > build native java for FreeBSD.
> 
> # cd /usr/ports/java/jdk13
> # make install clean

That's what I meant; it didn't work for me.  It got pretty far
through the build but seemed to run out of some sort of resource.
I couldn't tell by the error message what it was, and I don't
have the log anymore.

I'll try again.

-- 
Dan Eischen