From owner-freebsd-ports@FreeBSD.ORG Sat Feb 7 04:15:18 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6763216A4E5 for ; Sat, 7 Feb 2004 04:15:18 -0800 (PST) Received: from postman.arcor.de (newsread1.arcor-online.net [151.189.0.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6B2443D1D for ; Sat, 7 Feb 2004 04:15:17 -0800 (PST) (envelope-from eikemeier@fillmore-labs.com) Received: from fillmore.dyndns.org (port-212-202-51-21.reverse.qsc.de [212.202.51.21]) (authenticated bits=0)i17CFAtw022499 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 7 Feb 2004 13:15:11 +0100 (MET) Received: from [172.16.0.2] (helo=fillmore-labs.com) by fillmore.dyndns.org with esmtp (Exim 4.30; FreeBSD) id 1ApRMc-0006g6-Mj; Sat, 07 Feb 2004 13:15:10 +0100 Message-ID: <4024D6CD.5060706@fillmore-labs.com> Date: Sat, 07 Feb 2004 13:15:09 +0100 From: Oliver Eikemeier Organization: Fillmore Labs GmbH - http://www.fillmore-labs.com/ MIME-Version: 1.0 To: Gerald Pfeifer References: <4022D750.1040803@fillmore-labs.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: ports@freebsd.org Subject: Re: make versus _MANPAGE X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2004 12:15:18 -0000 Gerald Pfeifer wrote: > On Fri, 6 Feb 2004, Oliver Eikemeier wrote: > >>>I am currently fighting a very nasty problem where a construct involving >>>.for in a Makefile works as expected, depending on whether I use it before >>>.include or after. >> >>[...] >>.for evaluates its arguments immediately, not delayed. _MANPAGES is >>defined in bsd.port.pre.mk, so it is only defined *afterwards*. Works >>as advertised. > > Thanks for the explanation! > > So this _never_ could have worked, and we were just lucky in that none > of our users noticed/reported the problem before? Where do you use it? I *strongly* suggest that you look for an alternative, this scheme may break if bsd.port.mk is reorganized. > (Where could I have found the semantics of .for documented? The make > man page was not very helpful.) http://www.oreilly.com/catalog/make2/ file:///usr/share/doc/psd/12.make/paper.ascii.gz IEEE Std 1003.2-1992 (POSIX.2 Shell & Tools) Sorry, make is not well documented in the base system. -Oliver