From owner-freebsd-stable@FreeBSD.ORG  Sun Mar 14 22:59:51 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 742A516A4CE
	for <freebsd-stable@FreeBSD.org>;
	Sun, 14 Mar 2004 22:59:51 -0800 (PST)
Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6268743D45
	for <freebsd-stable@FreeBSD.org>;
	Sun, 14 Mar 2004 22:59:51 -0800 (PST)
	(envelope-from mbsd@pacbell.net)
Received: from atlas (adsl-64-166-22-245.dsl.snfc21.pacbell.net
	[64.166.22.245])i2F6xogg015113;	Sun, 14 Mar 2004 22:59:50 -0800 (PST)
Date: Sun, 14 Mar 2004 22:59:50 -0800 (PST)
From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net>
X-X-Sender: mikko@atlas.home
To: Joe Halpin <j.p.h@comcast.net>
In-Reply-To: <4054D78F.6080003@comcast.net>
Message-ID: <20040314225559.B52379@atlas.home>
References: <4054D78F.6080003@comcast.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-stable@FreeBSD.org
Subject: Re: 4.9-STABLE and m4
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Mar 2004 06:59:51 -0000

On Sun, 14 Mar 2004, Joe Halpin wrote:

> I'm working with the cURL project (http://curl.haxx.se), and I setup a
> daily build on my 4.9-RELEASE machine. Things were going fine until I
> upgraded to 4.9-STABLE. At that point the daily builds started failing.
>
> As far as I can tell the reason for that was that /usr/bin/m4 was
> somehow different from the same version on the FSF web site. I
> downloaded and built m4 from the FSF web site and installed it in
> /usr/local/bin (which is at the beginning of my PATH) and then the build
> started working again.
>
> Can anyone here confirm or deny my hypothesis? Any information would be
> welcome as I'd like to understand what happened.

If you are working on code that depends on GNU-isms in m4, you will
indeed need GNU m4.  Install the port (devel/m4), and look at how
other ports handle this requirement, for example autoconfuse^Wautoconf.

   $.02,
   /Mikko