From owner-freebsd-java@FreeBSD.ORG  Fri Dec 17 21:58:53 2004
Return-Path: <owner-freebsd-java@FreeBSD.ORG>
Delivered-To: freebsd-java@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DD92916A4CE
	for <freebsd-java@freebsd.org>; Fri, 17 Dec 2004 21:58:53 +0000 (GMT)
Received: from mx2.netflix.com (mail2.netflix.com [216.35.131.152])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B5E2D43D45
	for <freebsd-java@freebsd.org>; Fri, 17 Dec 2004 21:58:53 +0000 (GMT)
	(envelope-from nsayer@kfu.com)
Received: from [172.22.8.180] ([172.22.8.180])
	by mx2.netflix.com (8.12.8/8.12.8) with ESMTP id iBHLwqwL027166
	for <freebsd-java@freebsd.org>; Fri, 17 Dec 2004 13:58:53 -0800
Message-ID: <41C3569C.1040402@kfu.com>
Date: Fri, 17 Dec 2004 13:58:52 -0800
From: Nick Sayer <nsayer@kfu.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041111
X-Accept-Language: en-us, en
MIME-Version: 1.0
Cc: freebsd-java@freebsd.org
References: <4885A5C3-5041-11D9-A430-000A959D8ECE@kfu.com>
	<dcb2c27a041217102812fe62d1@mail.gmail.com>
In-Reply-To: <dcb2c27a041217102812fe62d1@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Still cannot build native JDK 1.4 with FreeBSD 5.3
X-BeenThere: freebsd-java@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting Java to FreeBSD <freebsd-java.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-java>
List-Post: <mailto:freebsd-java@freebsd.org>
List-Help: <mailto:freebsd-java-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-java>,
	<mailto:freebsd-java-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Dec 2004 21:58:54 -0000

Now I'm really messed up.

I was able to build the 1.4 JDK at home with no problems. I made that 
JDK into a package, then shipped it to my work machine and installed it.

Then I tried to build the JDK on the work machine and it failed in 
precisely the same way it has been all along.

What @#&!&^%#&! gremlin is in my machine that is making this happen?

And yet, so far as I can tell, the JDK appears to be perfectly 
operational here on my work machine. I can do anything I want with 
it.... except bootstrap the JDK port!