Date: Sat, 7 Feb 2004 12:45:12 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: Oliver Eikemeier <eikemeier@fillmore-labs.com> Cc: ports@freebsd.org Subject: Re: make versus _MANPAGE Message-ID: <Pine.BSF.4.58.0402071239250.13746@acrux.dbai.tuwien.ac.at> In-Reply-To: <4022D750.1040803@fillmore-labs.com> References: <Pine.BSF.4.58.0402052304380.74479@acrux.dbai.tuwien.ac.at> <4022D750.1040803@fillmore-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <bsd.port.post.mk> 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 could I have found the semantics of .for documented? The make man page was not very helpful.) Gerald -- Gerald Pfeifer (Jerry) gerald@pfeifer.com http://www.pfeifer.com/gerald/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.58.0402071239250.13746>