From owner-freebsd-openoffice@FreeBSD.ORG Fri Aug 13 09:52:54 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 E1F4016A4CE for ; Fri, 13 Aug 2004 09:52:54 +0000 (GMT) Received: from dd2718.kasserver.com (dd2718.kasserver.com [81.209.184.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EBEE43D41 for ; Fri, 13 Aug 2004 09:52:54 +0000 (GMT) (envelope-from freebsd@chillt.de) Received: from [192.168.0.7] (dsl-082-083-133-186.arcor-ip.net [82.83.133.186]) by dd2718.kasserver.com (Postfix) with ESMTP id BBEE7BB507; Fri, 13 Aug 2004 11:52:50 +0200 (CEST) Message-ID: <411C8F7C.90004@chillt.de> Date: Fri, 13 Aug 2004 11:53:00 +0200 From: Bartosz Fabianowski User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040807) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <200408120119.i7C1JRbC018760@gw.catspoiler.org> <411AD533.6000406@chillt.de> <411AE7B3.5020009@chillt.de> <411B76BF.8000601@chillt.de> <20040813085634.GD423@cirb503493.alcatel.com.au> In-Reply-To: <20040813085634.GD423@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: openoffice@freebsd.org Subject: Re: -CURRENT fixes 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: Fri, 13 Aug 2004 09:52:55 -0000 > Are you sure your hardware is totally OK? Building OOo is a much > bigger stress test than buildworld and instability might be a sign > of flaky hardware. Yep, I am quite certain it's related to -CURRENT. It's got to do with the scheduler changes and keeps getting better every time I cvsup world. I am now building openoffice-1.1-devel on yesterday's -CURRENT with no problems so far. > I got exactly the same thing on -STABLE. I tried comparing the > two $HOME/OpenOffice.org* directories but didn't see anything > interesting before I gave up. Maybe it's got to do with how the language sub ports are being built now? Some change in that infrastructure might have triggered it. - Bartosz