[PHP4BETA] Configuration problems with "kitchen sink" PHP installation

Being new to this list, I am not familiar with its social dynamics; also, I am a big booster for open source software, and have the highest regard for the terrific contribution being made by all the volunteer labor on PHP, so please don't misunderstand the following questions (a flame war is the last thing I intend to set off ;^): 1) I posted a rather detailed summary of failed configuration attempts (appended again below) but have not received a peep from a soul; is this sort of message premature, or uninteresting, or unhelpful? Let me know what I could do to make it a better contribution to the advance of PHP 4. 2) Given the current state of PHP 4, would it not be more accurate to refer to it as a late alpha release, rather than beta? Thanks and Best Regards, Rick Rodgers ----- Begin Included Message ----- From php4beta-return-9499-rodgers=nlm.nih.gov@lists.php.net Thu Jan 27 23:12:43 2000 Mailing-List: contact php4beta-help@lists.php.net; run by ezmlm Delivered-To: mailing list php4beta@lists.php.net Date: Thu, 27 Jan 2000 23:12:36 -0500 (EST) From: "R. P. Channing Rodgers, M.D." <rodgers@nlm.nih.gov> To: php4beta@lists.php.net Cc: rodgers@billings.nlm.nih.gov X-Sun-Charset: US-ASCII Subject: [PHP4BETA] Configuration problems with "kitchen sink" PHP installation Content-Length: 4528 Dear PHP Colleagues, I have attempted to build a "kitchen sink" PHP 4 installation -- using virtually all of the various packages which it claims to interact with. Here is the fullest configuration command which works: CPPFLAGS=-I/depot/include \ LDFLAGS=-L/depot/lib \ ./configure \ --prefix=/site/subsys/www/php_4.0b3 \ --with-config-file-path=/site/subsys/www/php_4.0b3 \ --with-apxs=/site/subsys/www/apache_1.3.9/bin/apxs \ --with-mysql=/site/subsys/www/mysql_3.22.27 \ --with-exec-dir=/site/subsys/www/apache_1.3.9/php-bin \ --enable-track-vars \ --disable-short-tags \ --enable-bcmath=yes \ --with-mcrypt=/depot/package/mcrypt_2.2.5 \ --with-mhash=/depot/package/mhash_0.6.1 \ --with-ftp \ --with-java=/usr/java \ --with-gd=shared,/depot/package/gd_1.7.3 \ --with-gdbm=/depot/package/gdbm_1.8 \ --with-ldap=/depot/package/openLDAP_1.4 \ --with-pdflib=/depot/package/pdflib_2.01 \ --with-jpeg-dir=/depot/package/jpeg_6b \ --with-tiff-dir=/depot/package/tiff_3.4b037 \ --with-readline=/depot/package/readline_4.0 \ --with-gettext=/depot/package/gettext_0.10.35 \ --enable-sysvshm=yes \ --enable-sysvsem=yes \ --enable-safe-mode=yes and here is a list of other configuration flags which failed, along with the messages produced. Does anyone have any insight as to what went wrong here? Some appear to be genuine configure script bugs, perhaps others are due to misunderstandings on my part, which may suggest needed documentation improvements. Note that we use the depot shared software repository scheme for locally installed software, explaining the paths you will observe below: FLAG: --with-zlib=/depot/package/zlib_1.1.3 \ RESULT: checking for gzgets in -lz... no configure: error: Zlib module requires zlib >= 1.0.9. COMMENT: As you can see, I am using zlib 1.1.3, with is >= 1.0.9 FLAG: --with-aspell=/depot/package/aspell_.28.3 \ RESULT: checking for ASPELL support... configure: error: Could not find aspell-c.h in /depot/package/aspell_.28.3/include - please copy it manually from the aspell sources to /depot/package/aspell_.28.3/include COMMENT: The problem here was aspell installed the header files in /depot/package/aspell_.28.3/include/aspell (which, incidentally, makes things tidier for the depot system), but configure would not find the file aspell-c.h there, after aspell-c.h was copied there manually. Thus we had to move the header files up into /depot/package/aspell_.28.3/include. Perhaps configure was desinged for an earlier release of spell? FLAG:--with-mm=/site/subsys/www/mm_1.0.12 \ RESULT: checking for mm support... configure: error: cannot find mm library COMMENT: I don't understand what is wrong: we do have a file /site/subsys/www/mm_1.0.12/lib/libmm.la FLAG: --with-imap=../imap_4.7a/c-client RESULT: checking for IMAP support... configure: error: could not find mail.h in ../imap_4.7a/c-client/include ! COMMENT: I used the Univ. of Wash. imap system. I find the two (identical) files in the IMAP source directory, ../imap_4.7a: ./src/c-client/mail.h ./c-client/mail.h whereas the configuration script appears to be expecting to find it in a path ending with "/include" FLAG: --with-xml=shared,/site/subsys/www/expat_1.1 \ RESULT: checking host system type... Configuration name missing. Usage: ./config.sub CPU-MFR-OPSYS or ./config.sub ALIAS where ALIAS is a recognized configuration type. checking build system type... Configuration name missing. Usage: ./config.sub CPU-MFR-OPSYS or ./config.sub ALIAS where ALIAS is a recognized configuration type. COMMENT: I have not got a CLUE as to what the problem is here, sorry! 8^) I'm still working on getting the new Berkeley db 3.X to install, so have not yet been able to test the --with-db2 flag. Note that this mesage applies only to success with "configure" and does not address the later stages of actually building PHP or running it. Thanks in advance for any help! Cheerio, Rick Rodgers -- PHP 4.0 Beta Mailing List <http://www.php.net/version4/> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net For additional commands, e-mail: php4beta-help@lists.php.net To contact the list administrators, e-mail: php4beta-admin@lists.php.net ----- End Included Message -----