Date: Wed, 24 Oct 2001 22:27:38 -0700 From: Bill Fenner <fenner@research.att.com> To: drosih@rpi.edu Cc: ade@freebsd.org, portmgr@freebsd.org, arch@freebsd.org Subject: Re: Switch to newer AUTOCONF, and fixing ports Message-ID: <200110250527.WAA14597@windsor.research.att.com> References: <200110242107.OAA09339@windsor.research.att.com> <20011024205654.E3080@FreeBSD.org> <p05101010b7fd2df7277b@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110250527.WAA14597>