From owner-freebsd-openoffice@FreeBSD.ORG Sat Feb 21 03:09:27 2004 Return-Path: Delivered-To: freebsd-openoffice@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 64F8F16A4CE; Sat, 21 Feb 2004 03:09:27 -0800 (PST) Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0A3F43D31; Sat, 21 Feb 2004 03:09:26 -0800 (PST) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id i1LB9H41048299; Sat, 21 Feb 2004 12:09:18 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Sat, 21 Feb 2004 12:09:17 +0100 (CET) From: Martin Blapp To: Kris Kennaway In-Reply-To: <20040221035340.GA41491@xor.obsecurity.org> Message-ID: <20040221120600.Q6179@cvs.imp.ch> References: <20040221030343.1f0ce596.gautam@inspired.net.au> <20040221134822.60862fc2.gautam@inspired.net.au> <20040221143825.4ec73b52.gautam@inspired.net.au> <20040221035340.GA41491@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scan: smtp-vilter X-SMTP-Vilter-Version: 1.1.0rc2 X-SMTP-Vilter-Backend: Clam AntiVirus Daemon (clamd) X-SMTP-Vilter-Status: clean cc: Gautam Gopalakrishnan cc: freebsd-ports@freebsd.org cc: openoffice@freebsd.org Subject: Re: Openoffice 1.1 not building X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Feb 2004 11:09:27 -0000 Hi, > That's completely wrong, USE_GCC is not to be set by the user. > > Unfortunately for your problem, I think the Openffice maintainers are > inactive at the moment (at least, I haven't heard from them in several > weeks about an unrelated problem with the ports). Since we check USE_GCC inside the openoffice port for the correct values and set CXX=${CXX} CC=${CC} depending on OS-version, I don't see why it is completly wrong. Of course I can also rename it to HAVE_GCC or something like this. OOO build is broken with severall OS GCC versions, and with severall port GCC version, so we definitly need to check which gcc we have to use for which OS-version. Martin