Date: Sat, 11 Jan 2003 00:50:16 +0100 From: Thomas Moestl <tmoestl@gmx.net> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Scott Long <scott_long@btc.adaptec.com>, re-builders@freebsd.org Subject: Re: Something's wrong with ports/devel... Message-ID: <20030110235016.GG1732@crow.dom2ip.de> In-Reply-To: <20030110230233.GA1296@athlon.pn.xcllnt.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <tmoestl@gmx.net> http://www.tu-bs.de/~y0015675/
<tmm@FreeBSD.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030110235016.GG1732>