From owner-freebsd-arch  Wed Oct 24 22:27:44 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 45A2E37B401; Wed, 24 Oct 2001 22:27:41 -0700 (PDT)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 79FB54CE56; Thu, 25 Oct 2001 01:27:40 -0400 (EDT)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id BAA21081;
	Thu, 25 Oct 2001 01:27:39 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.8.8+Sun/8.8.5) id WAA14597;
	Wed, 24 Oct 2001 22:27:39 -0700 (PDT)
Message-Id: <200110250527.WAA14597@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: drosih@rpi.edu
Subject: Re: Switch to newer AUTOCONF, and fixing ports
Cc: ade@freebsd.org, portmgr@freebsd.org, arch@freebsd.org
References:  <200110242107.OAA09339@windsor.research.att.com> <20011024205654.E3080@FreeBSD.org> <p05101010b7fd2df7277b@[128.113.24.47]>
Date: Wed, 24 Oct 2001 22:27:38 -0700
Versions: dmail (solaris) 2.2j/makemail 2.9b
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-arch.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-arch>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-arch>
X-Loop: FreeBSD.ORG


I wrote a script that does "make configure" on all USE_AUTOCONF ports
with autoconf 2.52 installed; it's only gotten to japanese/esecanna-mod
but 48 out of 94 ports have failed.  This includes 15 on which it was
the "./configure" run itself that failed, so it's only 33 that failed
on the autoconf step; the other 15 need more examination to determine
if it's my host environment or the new autoconf that caused the failure.

(It will try with 2.13.000227 next; presumably those results will be
available in the morning.)

Don't forget that this 33% failure rate will affect people who use
FreeBSD to develop other software too.  e.g. tcpdump, libpcap, tcpslice,
all fail either autoheader or autoconf with 2.52.  It's also non-obvious
in some circumstances how to write autoconf scripts that work both with
2.13 and 2.52.

  Bill

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message