From owner-freebsd-openoffice@FreeBSD.ORG Thu Dec 30 05:10:26 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 C189216A4CE for ; Thu, 30 Dec 2004 05:10:26 +0000 (GMT) Received: from satie.private.org (qclgw.qcl.t.u-tokyo.ac.jp [133.11.70.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CD9D43D4C for ; Thu, 30 Dec 2004 05:10:25 +0000 (GMT) (envelope-from chat95@mac.com) Received: from localhost (localhost [IPv6:::1]) by satie.private.org (8.13.1/8.13.1) with ESMTP id iBU59ggi063129; Thu, 30 Dec 2004 14:09:43 +0900 (JST) (envelope-from chat95@mac.com) Date: Thu, 30 Dec 2004 14:09:42 +0900 (JST) Message-Id: <20041230.140942.115917626.chat95@mac.com> To: mi+mx@aldan.algebra.com From: NAKATA Maho In-Reply-To: <200412291902.31047.mi+mx@aldan.algebra.com> References: <200412291902.31047.mi+mx@aldan.algebra.com> Organization: private X-Mailer: Mew version 3.3 on XEmacs 21.4.14 (Reasonable Discussion) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: openoffice@gentoo.org cc: openoffice@freebsd.org Subject: Re: OOo-1.1.4 and gcc-3.4 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: Thu, 30 Dec 2004 05:10:26 -0000 In Message-ID: <200412291902.31047.mi+mx@aldan.algebra.com> Mikhail Teterin wrote: Hello Mikhail First of all thank you very much for your effort! It was largest I ever see! However, I'm on a vacation until 2005/Jan/20 please wait for while I also have a ready port for 1.1.4 :) > building OOo with gcc-3.4.x. Okay, this is one of the major part of your upgrade. Can we sure this version of gcc works? (please see the commit log of lang/gcc-ooo, and once 3.3.1 has a bug which prohibit to run OOo 1.1.1a...it was due to gcc's bug) > 1. make use of their work; Okay, are they JCA signed person and patches have #iZ? I glanced your patch OOo-GCC-3.4.patch.bz2, but I don't see #iZ any part of it. > 2. use system's nas, curl, zlib, freetype, mspack, and -- most importantly -- > stlport; I think these should be activated via special build flags. My concern is, how do we take care of them? Building OOo is always fragile. Please imagine if STLport is upgraded and break OOo build. Or a situation STLport cannot be upgraded since it can broke OOo build. Well, it can be done by setting MAINTAINER as openoffice@freebsd.org so that we can control everything :) however this costs too much for me. > 3. build OOo-1.1.4. Wonderful! Anyway, thank you very much for your contribution! -- NAKATA, Maho