PHP 4.0 Bug #6521 Updated: phpize or related broken: no Makefile produced after ./configure

From: Date: Mon, 09 Oct 2000 15:42:55 +0000
Subject: PHP 4.0 Bug #6521 Updated: phpize or related broken: no Makefile produced after ./configure
Groups: php.dev 
Request: Send a blank email to php-dev+get-34508@lists.php.net to get a copy of this message
ID: 6521 Updated by: sniper Reported By: troels@arvin.dk Status: Closed Bug Type: *General Issues Assigned To: Comments: already fixed in CVS, per 4.0.3RC2 Previous Comments: --------------------------------------------------------------------------- [2000-09-03 22:20:35] troels@arvin.dk This has worked in PHP 4 releases prior to 4.0.2: After a PHP install, you could copy a PHP extension like gettext (which is properly prepared for being a self-contained extension) to a temporary directory and do phpize ./configure --with-gettext=shared This produced a working Makefile. An example of another extension that would work like this: zlib. Since 4.0.2, the phpize+./configure steps do not produce a Makefile. If the extension's Makefile.in is copied to Makefile and the following lines How PHP was installed: Grabbed latest CVS, to ./buildconf and "./configure --with-apxs=/usr/sbin/apxs"; make install On other words: A quite normal installation without any bells/whistles. Analysis: The only file which seems to be missing is the Makefile. If Makefile.in is copied to Makefile and the following lines are added in the beginning of the file, then the self-contained extension compiles without errors: top_srcdir = . top_builddir = $(top_srcdir) srcdir = $(top_srcdir)/ builddir = $(top_srcdir)/ VPATH = $(top_srcdir)/ --------------------------------------------------------------------------- Full Bug description available at: http://bugs.php.net/?id=6521

« previous php.dev (#34508) next »