From owner-freebsd-openoffice@FreeBSD.ORG  Fri Jul 21 10:35:31 2006
Return-Path: <owner-freebsd-openoffice@FreeBSD.ORG>
X-Original-To: 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 BDBD116A4E0
	for <openoffice@freebsd.org>; Fri, 21 Jul 2006 10:35:31 +0000 (UTC)
	(envelope-from freebsd@chillt.de)
Received: from dd2718.kasserver.com (dd2718.kasserver.com [81.209.184.159])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3C69843D4C
	for <openoffice@freebsd.org>; Fri, 21 Jul 2006 10:35:31 +0000 (GMT)
	(envelope-from freebsd@chillt.de)
Received: from [127.0.0.1] (dslb-084-061-204-024.pools.arcor-ip.net
	[84.61.204.24])
	by dd2718.kasserver.com (Postfix) with ESMTP id 6A997CEFF1;
	Fri, 21 Jul 2006 12:35:21 +0200 (CEST)
Message-ID: <44C0ADF0.2090807@chillt.de>
Date: Fri, 21 Jul 2006 12:35:28 +0200
From: Bartosz Fabianowski <freebsd@chillt.de>
User-Agent: Thunderbird 1.5.0.4 (X11/20060605)
MIME-Version: 1.0
To: NAKATA Maho <chat95@mac.com>
References: <44BFF1CD.1040901@chillt.de>
	<20060721.143843.74749745.chat95@mac.com>
In-Reply-To: <20060721.143843.74749745.chat95@mac.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: openoffice@freebsd.org
Subject: Re: lang/gcc41-withgcjawt does not actually work
X-BeenThere: freebsd-openoffice@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting OpenOffice to FreeBSD <freebsd-openoffice.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice>, 
	<mailto:freebsd-openoffice-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-openoffice>
List-Post: <mailto:freebsd-openoffice@freebsd.org>
List-Help: <mailto:freebsd-openoffice-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice>, 
	<mailto:freebsd-openoffice-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jul 2006 10:35:31 -0000

> still its build is broken.
> 
> do you know something about it?

I have never seen this error. Maybe it has something to do with the 
question *when* to replace libtool? You probably copied the system 
libtool to the two directories at the start of the build so that they 
got used all the time. I do it differently. I let the build run until it 
fails and only at that point replace the libtool executable that 
produced an error.

Maybe this way, the libtool call that gave you an error got executed by 
the system libtool for you but the built-in one for me? That might make 
a difference... Other than that, I have absolutely no idea.

- Bartosz