From owner-freebsd-java@FreeBSD.ORG Sat Aug 23 07:19:32 2003 Return-Path: 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 9613A16A4BF for ; Sat, 23 Aug 2003 07:19:32 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2AF943F85 for ; Sat, 23 Aug 2003 07:19:31 -0700 (PDT) (envelope-from eischen@vigrid.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 h7NEJUUK021285; Sat, 23 Aug 2003 10:19:31 -0400 (EDT) Date: Sat, 23 Aug 2003 10:19:30 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Sheldon Hearn In-Reply-To: <20030823075750.GB47245@starjuice.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: java@freebsd.org Subject: Re: jdk14 on -current X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: deischen@freebsd.org List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Aug 2003 14:19:32 -0000 On Sat, 23 Aug 2003, Sheldon Hearn wrote: > On (2003/08/23 09:55), Sheldon Hearn wrote: > > > On (2003/08/22 22:33), Daniel Eischen wrote: > > > > > Has anyone tried building jdk14 on -current. I've never been > > > lucky enough to get it to build. It seems to be failing now > > > because of the compiler: > > > > It built fine before the second-last gcc upgrade to 3.3.1. :-( > > There was supposed to be more. > > I meant that the build failures started with gcc version 3.3.1 [FreeBSD] > 20030711 (prerelease). > > It may be that 3.3.1 release magically resupports the broken C++ syntax, > but I'm not hopeful. As our base compiler, I doubt it. The port may; IIRC, the port is not as strict as our base compiler. > I recall that someone said he was working on this, but can't remember > who. I may be wrong. I think it's just improper use of concatenation, as in foo##bar, where foo is . I think the fix is to just remove ##. -- Dan Eischen