From owner-freebsd-openoffice@FreeBSD.ORG Thu Aug 12 01:19:34 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 17FAD16A4CE for ; Thu, 12 Aug 2004 01:19:34 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCEB443D39 for ; Thu, 12 Aug 2004 01:19:33 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.11/8.12.11) with ESMTP id i7C1JRbC018760 for ; Wed, 11 Aug 2004 18:19:31 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200408120119.i7C1JRbC018760@gw.catspoiler.org> Date: Wed, 11 Aug 2004 18:19:27 -0700 (PDT) From: Don Lewis To: openoffice@FreeBSD.org In-Reply-To: <411AC38D.9010109@chillt.de> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Subject: Re: openoffice-1.1 build more broken than usual on 5.2-CURRENT 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, 12 Aug 2004 01:19:34 -0000 On 12 Aug, Bartosz Fabianowski wrote: >> gmake[3]: Entering directory `/usr/ports/editors/openoffice-1.1/work/mozilla/work/mozilla/nsprpub/config' >> gcc32 -o now.o -c -O -pipe now.c >> now.c:45:2: #error "Architecture not supported" >> now.c:123:2: #error "Architecture not supported" > [snip] > >> I think the trigger for the breakage was the recent changes to make's >> handling of MAKEFLAGS in 5.2-CURRENT. > > I have been wondering for a while what change in -CURRENT actually broke > the openoffice-1.1 port. When I last tried to compile the port on my > system, it died at the very same point as your build. I was able to get > mozilla to compile by simply cd'ing into the slave port directory and > running "make clean && make" in there. So, the problem must be with some > flag being passed from the main port's make to the mozilla slave port's > make. > > Now, the curious thing here is that the ports actually use gmake. How > can that be affected by changes to FreeBSD's own make? The change to FreeBSD's make is supposed to have made it conform to POSIX. When CFLAGS (or any other variable) is specified on the command line, this variable assignment is also stashed in the MAKEFLAGS environment variable, which gets passed to all the submakes, and keeps CFLAGS (or whatever) from being modified by doing variable assignments in the Makefiles. Maybe gmake already behaved this way and the only reason we didn't have this problem before was that FreeBSD's make didn't pass MAKEFLAGS through the environment to the top level gmake.