Date: Fri, 14 Nov 2003 02:27:08 +0100 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: obrien@FreeBSD.org Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: ports/59254: ports that write something after bsd.port.mk Message-ID: <3FB42F6C.8000706@fillmore-labs.com> In-Reply-To: <20031114011128.GA38924@dragon.nuxi.com> References: <3FB39FB5.5000209@fillmore-labs.com> <20031113164741.GA33494@dragon.nuxi.com> <3FB40710.8010409@fillmore-labs.com> <20031114011128.GA38924@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > On Thu, Nov 13, 2003 at 11:34:56PM +0100, Oliver Eikemeier wrote: > >>You are right with CONFIGURE_TARGET, 359 ports use a workaround, thanks >>again for bringing this up. I'm using this workaround myself in the >>OpenLDAP ports, and PR 52917 seems to deal with it. At least it should >>be easy to remove the workaround from those ports, they all use the >>same assignment, so it's just a simple search-and-replace. > > Maybe we need a knob (USE_NEW_CONFIGURE_TUPLE) or something so that > there is complete consistency in the GNU tuple string. OR make it dependend on GNU_CONFIGURE/HAS_CONFIGURE or use GNU_CONFIGURE= new but we should discuss this as a followup of PR 52917
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FB42F6C.8000706>