Date: Fri, 12 Mar 2004 17:42:17 -0800 From: Ade Lovett <ade@FreeBSD.org> To: Alex Dupre <ale@FreeBSD.org> Cc: ports@FreeBSD.org Subject: Re: Problems compiling Apache2 under 5.2.1-P1 Message-ID: <1079142137.344.13.camel@reaper.lovett.com> In-Reply-To: <4051B6B8.7050001@FreeBSD.org> References: <95692348.1079092312@[10.122.7.143]> <20040312130326.7f63cf21.clement@FreeBSD.org> <100948596.1079097568@[10.122.7.143]> <20040312140414.7469562c.clement@FreeBSD.org> <4051B6B8.7050001@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2004-03-12 at 05:10, Alex Dupre wrote: > I suspected it. I don't know why he did this change before committing > bsd.autotools.mk. Now we have a bunch of broken ports. Curious, because (a) this was an effective null-op commit and (b) apache2 still compiles on both the machine with the existing autotools infrastructure, and on the one with the new bsd.autotools.mk (both running 5.2-CURRENT). We most certainly do NOT have "a bunch of broken ports" as a result of this. If there are specific examples, then let me know, with FULL logs. The next "null-op" commit is a traversal of the tree, removing references to the generic USE_{LIBTOOL,AUTOCONF,AUTOMAKE} and replacing them with the default USE_<x>_VER values, at which point, USE_LIBTOOL/USE_AUTOCONF/USE_AUTOMAKE will be put into a de-orbit burn sequence. -aDe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1079142137.344.13.camel>