From owner-freebsd-openoffice@FreeBSD.ORG Thu May 25 16:54:12 2006 Return-Path: X-Original-To: freebsd-openoffice@FreeBSD.org 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 2260916A72C for ; Thu, 25 May 2006 16:54:12 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D84143D77 for ; Thu, 25 May 2006 16:54:07 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id k4PGriwV011125; Thu, 25 May 2006 12:53:44 -0400 (EDT) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-openoffice@FreeBSD.org Date: Thu, 25 May 2006 12:53:25 -0400 User-Agent: KMail/1.6.2 References: <4475AD72.3060302@cnptia.embrapa.br> <200605251240.13725.jkim@FreeBSD.org> In-Reply-To: <200605251240.13725.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200605251253.27542.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88/1484/Thu May 25 11:19:23 2006 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Carlos Fernando Assis Paniago Subject: Re: compilation erro in OOo-2.0-devel and amd64 and freebsd 6.1 X-BeenThere: freebsd-openoffice@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting OpenOffice to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 May 2006 16:54:16 -0000 On Thursday 25 May 2006 12:40 pm, Jung-uk Kim wrote: > On Thursday 25 May 2006 09:13 am, Carlos Fernando Assis Paniago wrote: > > The compilation was done ok. If I try to execute the > > openoffice.org-SRC680_m169 it stops in the registration processs. > > I went and remove the .open* directory, but it isn't working. > > That is the reason that I was compiling with DEBUG to try do > > debug the process. Do you have any solutions? > > I am sorry to hear that. Are you using Gnome or KDE? I had > problems with Gnome (I am quite confident that's atk related) but > with KDE, it was okay, i.e., I was able to run swrite and all. I just finished building 2.0.3rc3 and I see the same problem as yours on KDE. :-( Something's broken between m168 and m169, I guess. I swear I tested m169 but I have no idea why it's broken now. :-( I'll let you know as soon as I find something. Jung-uk Kim