Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:15655 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82124 invoked by uid 1010); 29 Mar 2005 12:48:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 82107 invoked from network); 29 Mar 2005 12:48:03 -0000 Received: from unknown (HELO sigpipe.cz) (127.0.0.1) by localhost with SMTP; 29 Mar 2005 12:48:03 -0000 X-Host-Fingerprint: 62.245.70.224 r2g224.chello.upc.cz FreeBSD 4.6-4.9 Received: from ([62.245.70.224:4615] helo=isis.sigpipe.cz) by pb1.pair.com (ecelerity HEAD r(5268)) with SMTP id AA/73-16973-18E49424 for ; Tue, 29 Mar 2005 07:48:01 -0500 Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 17CA11F87BEE; Tue, 29 Mar 2005 14:47:58 +0200 (CEST) Date: Tue, 29 Mar 2005 14:47:58 +0200 To: Jani Taskinen Cc: Jon Parise , internals@lists.php.net Message-ID: <20050329124758.GD42955@isis.sigpipe.cz> References: <20050327221532.GA17108@csh.rit.edu> <20050329114511.GB42955@isis.sigpipe.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: [PHP-DEV] Build system support for stock FreeBSD autoconf ports From: neuhauser@sigpipe.cz (Roman Neuhauser) # sniper@iki.fi / 2005-03-29 15:24:07 +0300: > On Tue, 29 Mar 2005, Roman Neuhauser wrote: > > ># sniper@iki.fi / 2005-03-29 11:11:27 +0300: > >>On Sun, 27 Mar 2005, Jon Parise wrote: > >> > >>>The attached patch allows PHP's build system to recognize FreeBSD's > >>>"versioned" autoconf ports without the need for system-level symlinks > >>>or similar aliasing. It uses 'shtool path' to (attempt to) locate the > >>>appropriate autoconf / autoheader executable. > >> > >> I added such patch once but Sebastian got some problems with > >> it so it was reverted. And I don't want to add this patch > >> either unless there is very good reason to do so. > > > > It would be interesting to know what the problems were so that > > they could be ironed out. > > He had the problems with gentoo and it's autoconf wrapper crap. > > >> And finally: Common users should NEVER EVER run buildconf. > > > > But why make hacking PHP harder? > > And how is it hard atm to run './buildconf' ?? > If you have autoconf (any version above 2.13 works) installed, > there are no problems. I have autoconf-2.13, 2.53, 2.59, automake-1.4.5, 1.5, 1.9.4, libtool-1.3.5, 1.5.10. I have no executable named autoconf, automake, or libtool, instead, there are autoconf213, autoconf253, etc. Without symlinking or installing the desired versions somewhere and munging PATH, running ./buildconf is an uber-easy way to be informed that I don't have the required tools. Such schemes are quite common thanks to incompatibilities between autotools versions, e. g. Subversion's buildconf equivalent accepts the names from environment, mentioning IIRC Debian installing the tools as e. g. autoconf-213. -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991