From owner-freebsd-openoffice@FreeBSD.ORG Wed Oct 15 03:20:28 2003 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 E7CA316A4B3 for ; Wed, 15 Oct 2003 03:20:28 -0700 (PDT) Received: from mrelay2.uni-hannover.de (mrelay2.uni-hannover.de [130.75.2.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81FE643F3F for ; Wed, 15 Oct 2003 03:20:27 -0700 (PDT) (envelope-from quetschke@scytek.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2])h9FAJvf9013186; Wed, 15 Oct 2003 12:19:58 +0200 (MEST) Received: from scytek.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with ESMTP id 4A9F6274; Wed, 15 Oct 2003 12:19:51 +0200 (CEST) Message-ID: <3F8D1F46.6050403@scytek.de> Date: Wed, 15 Oct 2003 12:19:50 +0200 From: Volker Quetschke User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20030828 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@porting.openoffice.org References: <3F8B1626.8070406@scytek.de> <3F8BDE9F.7020801@sun.com> <20031014135525.GG30746@pmp.uni-hannover.de> In-Reply-To: <20031014135525.GG30746@pmp.uni-hannover.de> X-Enigmail-Version: 0.76.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.37 cc: openoffice@freebsd.org Subject: Re: [porting-dev] Build fails on NFS volume 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: Wed, 15 Oct 2003 10:20:29 -0000 (Crossposting to openoffice@freebsd.org because this might be of some interest) Problem was: openoffice-devel cannot be build on NFS. >>>- use NFS instead of local file system >> >>Aha, that sounds like a 'file locking over NFS' issue. > > Seems so. I just copied the whole tree to a local partition, and now > everything seems to compile fine (though it's far from being finished by now > :-). > >>I've seen such things before on Linux, when the NFS 'lockd' is not >>running (some / few distributions have / had too 'clever' NFS startup >>scripts, omitting to start 'lockd'). Just starting 'lockd' usually >>solved all NFS file locking problems. > > In my experience locking via NFS is a real pain. I've never seen a working > lockd on Linux or *BSD (only on commercial unices like Solaris :-). Perhaps > this has changed meanwhile. However, just starting lockd didn't help, but > maybe the system needs a reboot for this to work (the manpage is somewhat > ambiguous here :-). I'll reboot the system and try NFS with activated lockd/statd > as soon as the local compile has successfully finished. The NFS server is a FreeBSD 4.8 machine and despite of we started the rpc.lockd on that machine. That helped and the build continued .... Volker