Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 10 Dec 2008 00:28:43 -0800
From:      Maxim Sobolev <sobomax@sippysoft.com>
To:        pav@FreeBSD.org
Cc:        cvs-ports@FreeBSD.org, Alexey Dokuchaev <danfe@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org
Subject:   Re: cvs commit: ports/net/asterisk Makefile
Message-ID:  <493F7DBB.9040801@sippysoft.com>
In-Reply-To: <1228896975.34558.61.camel@pav.hide.vol.cz>
References:  <200812090602.mB962eiw090973@repoman.freebsd.org>	 <20081209191509.GA50518@FreeBSD.org> <493ED4B6.4010409@sippysoft.com>	 <1228858485.917.4.camel@hood.oook.cz> <493F16B1.3020409@sippysoft.com> <1228896975.34558.61.camel@pav.hide.vol.cz>

next in thread | previous in thread | raw e-mail | index | archive | help
Pav Lucistnik wrote:
> Maxim Sobolev píše v út 09. 12. 2008 v 17:09 -0800:
> 
>> OK, further investigation shows that it doesn't happen to OPTIONS added 
>> after .include <bsd.port.pre.mk>:
> 
>> .include <bsd.port.pre.mk>
>>
>> .if ${ARCH} == "i386" || ${ARCH} == "amd64"
>> OPTIONS+=       ZAPTEL          "Enable Zaptel support" off
>> .endif
>> -----
>>
>> Looks like a bug in bsd.port.mk to me.
> 
> Ah right, yeah, that's understandable given that OPTIONS processing is
> done in pre.mk, so you can have WITH_*/WITHOUT_* variables available
> between pre.mk and post.mk.

Hmm, any chance to change this? We need pre.mk in order to determine 
architecture that we are running on.

-Maxim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?493F7DBB.9040801>