From owner-freebsd-ports Tue Dec 25 20:15:59 2001 Delivered-To: freebsd-ports@freebsd.org Received: from squall.waterspout.com (squall.waterspout.com [208.13.56.12]) by hub.freebsd.org (Postfix) with ESMTP id 48EE737B419; Tue, 25 Dec 2001 20:15:55 -0800 (PST) Received: by squall.waterspout.com (Postfix, from userid 1050) id 71D319B08; Tue, 25 Dec 2001 23:13:37 -0500 (EST) Date: Tue, 25 Dec 2001 23:13:37 -0500 From: Will Andrews To: ports@FreeBSD.org Cc: stable@FreeBSD.org Subject: **HEADS UP** autoconf/automake issues in ports Message-ID: <20011225231337.M73815@squall.waterspout.com> Reply-To: Will Andrews Mail-Followup-To: ports@FreeBSD.org, stable@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi all, I should have done this 2 days ago, but now is better than never. Right now, if you upgrade your autoconf (devel/autoconf), you'll get autoconf 2.52. This is *known* to be broken with anything using automake if you do not have automake (devel/automake) 1.5 installed too. In other words, if ports/jane/johndoeport's distfile requires autoconf and automake to work, you MUST have sync'd versions of autoconf and automake. The problem is that the dependencies are slightly out of date in bsd.port.mk, so everything that sets USE_AUTOMAKE is really depending on autoconf213/automake14 (ports/devel/...). This has been fixed in an upcoming bsd.port.mk patch which has undergone testing on bento's 4-exp tree. So if you see any problems like the one reported here: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=355039+0+current/freebsd-questions ..the solution is to make sure you have autoconf 2.52 AND automake 1.5 installed, because in this case, the m4 macro that's missing is defined by am 1.5. Thanks, -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message