From owner-freebsd-ia64 Fri Jan 10 15:49: 1 2003 Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC67937B401 for ; Fri, 10 Jan 2003 15:48:58 -0800 (PST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9827743F3F for ; Fri, 10 Jan 2003 15:48:57 -0800 (PST) (envelope-from tmoestl@gmx.net) Received: (qmail 19234 invoked by uid 0); 10 Jan 2003 23:48:56 -0000 Received: from p508e7307.dip.t-dialin.net (HELO galatea.local) (80.142.115.7) by mail.gmx.net (mp016-rz3) with SMTP; 10 Jan 2003 23:48:56 -0000 Received: from localhost ([127.0.0.1] helo=galatea.local) by galatea.local with esmtp (Exim 4.10 #1) id 18X8us-0001Yu-00; Sat, 11 Jan 2003 00:50:22 +0100 Received: (from tmm@localhost) by galatea.local (8.12.6/8.12.6/Submit) id h0ANoG6q006003; Sat, 11 Jan 2003 00:50:16 +0100 (CET) Date: Sat, 11 Jan 2003 00:50:16 +0100 From: Thomas Moestl To: Marcel Moolenaar Cc: Scott Long , re-builders@freebsd.org Subject: Re: Something's wrong with ports/devel... Message-ID: <20030110235016.GG1732@crow.dom2ip.de> References: <20030110214547.GA1100@athlon.pn.xcllnt.net> <3E1F43AF.40002@btc.adaptec.com> <20030110222829.GA1196@athlon.pn.xcllnt.net> <20030110224115.GE1732@crow.dom2ip.de> <20030110230233.GA1296@athlon.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030110230233.GA1296@athlon.pn.xcllnt.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 2003/01/10 at 15:02:33 -0800, Marcel Moolenaar wrote: > On Fri, Jan 10, 2003 at 11:41:15PM +0100, Thomas Moestl wrote: > > > > > > It never get's past the "Applying :S ..." :-( > > > > > > There's no update for the makefile. Is this a genuine make(1) bug? > > > > See the attached patch. S///g does hang (unsurprisingly). > > This is a work-around, right? > > Put differently: is it the intention of the makefile writer to > replace the value of ${_CPUCFLAGS} with the empty string or is > it the intention to replace the literal "${_CPUCFLAGS} with the > empty string? My first patch was bogus (I was fooled by the combination of :=, :S and undefined values), the intent is to replace the value with the empty string. I've committed a working fix now; of course, make should probably just ignore S///g, but I guess that's nothing we want to fix in RELENG_5_0 right now :) - Thomas -- Thomas Moestl http://www.tu-bs.de/~y0015675/ http://people.FreeBSD.org/~tmm/ PGP fingerprint: 1C97 A604 2BD0 E492 51D0 9C0F 1FE6 4F1D 419C 776C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message