From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 17 04:20:47 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5480016A4CE; Tue, 17 Aug 2004 04:20:47 +0000 (GMT) Received: from robbins.dropbear.id.au (043.b.011.mel.iprimus.net.au [210.50.217.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A396A43D48; Tue, 17 Aug 2004 04:20:44 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 564084135; Tue, 17 Aug 2004 00:29:31 +1000 (EST) Date: Tue, 17 Aug 2004 00:29:31 +1000 From: Tim Robbins To: Craig Boston Message-ID: <20040816142931.GA18527@cat.robbins.dropbear.id.au> References: <20040813033048.GA33060@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040813033048.GA33060@nowhere> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org cc: smkelly@freebsd.org Subject: Re: m4 is broken -- can't rename builtins (patch in PR) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 04:20:47 -0000 On Thu, Aug 12, 2004 at 10:30:48PM -0500, Craig Boston wrote: > Hi -hackers: > > Just wondering if I could get a committer's attention to look at > bin/59883. It seems that m4 has been broken for quite some time -- at > least in the ability to rename builtin macros -- defn() doesn't work > correctly anymore. I've been using the simple patch in the PR locally > for the last several months and have yet to run into any problems with > it. I guess not many people use the bundled m4 for anything much more > complicated than making sendmail.cf files ;) > > I'm not sure who is the active maintainer for m4 is, or even if there is > one. CC: tjr & smkelly as they are the last couple people to touch the > code in a while. I hope I'm sending this to the right place :) I've just committed a temporary fix for this to -CURRENT, and will MFC it in about a week. I'll consider merging in the better (but more involved) OpenBSD fix and any other useful changes they've made, but this will have to wait until after 5.3-R. Thanks for bringing the problem to my attention. Tim