[LONG] Re: [PHP4BETA] Configuration problems with "kitchen sink" PHP installation

Sorry, list, I know this first part is off topic, but maybe it is something to be aware of in the future... > > I have never heard of "the depot shared software repository > > scheme", therefore I have very little input to offer! :) > > I hope you *will* hear of it eventually. The scheme was invented ~10 > years back by folks at NIST, and presented at USENIX conference. We > have been working with the folks at the Univ. Texas Advanced Research > Laboratory to create a suite of perl tools to manage the system. > It provides a much more powerful and disciplined way of managing local > software than the old /usr/local convention, and complements the Sun > pkg and Linux RPM packaging systems quite nicely. We hope to be > releasing it all under the GNU banner some time this year... > Out of curiosity, how does it compare/contrast with the Linux Standars Base? (See http://www.linuxbase.org/ for info). I personally hate all packaging systems with a passion, because I love the bleeding edge, and no packaging system has ever been able to keep up. > > > > 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 > > > > It seems to me that when you followed the reccomendation, things > > worked, right? So what's the concern? > > No, I did not express myself well. The default intrinsic behavior of > the aspell .28.3 package itself is to install the header files in > the directory <base_directory>/aspell/include, whereas the configuration > appears to be expecting them to appear in <base_directory>/include, so > I had to manually move everyting up one directory level. From Peter > Kovacs <php4-peter@knowpost.com> separate posting, it appears that PHP > may not work with versions later than about .26 anyway -- does anyone > know if there are plans to update to the latest versions? http://www.php.net/manual/ref.aspell.php3 has a note a/b the C interface being missing from newer versions of aspell. I found the following note @ http://aspell.sourceforge.net/manual/4_Library.html: "Unfortunately due to a major rewrite of the C++ library the C library is currently unavailable. I hope to have it back in a release or two." If the C interface is gine, so is PHP support, AFAIK. Therefore, there is not (yet) any point in changing auto(conf|make) settings, until this stabilizes. > > > > 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" > > > > > > > Do not pass the location of the imap source...it is looking for > > the installed version, in /usr/local/include, or equiv. > > Thanks -- this is an important point that is not made clearly in the > PHP installation documents -- that arguments to the flags are generally > the installed and not the source directories. However, in the case of > IMAP, this still does not solve the installation problem. The Univ. of > Washington IMAP package Makefile does not have an install target! > The instructions are concerned only with installing the 3 imap binaries > it creates, which you end up doing manually. There are no lib or > include directories discussed. If the PHP configuration is expecting > to find header files in hte IMAP installation tree, the PHP installation > documentation will have to specify which ones need to be installed and > where. I'll grant this info could be more readily available...feel free to contribute! :) Seriously, though, if you read http://www.php.net/manual/ref.imap.php3, you will see the following paragraph: "To get these functions to work, you have to compile PHP with --with-imap. That requires the c-client library to be installed. Grab the latest version from ftp://ftp.cac.washington.edu/imap/ and compile it. Then copy c-client/c-client.a to /usr/local/lib or some other directory on your link path and copy c-client/rfc822.h, mail.h and linkage.h to /usr/local/include or some other directory in your include path." Before attempting something like a "kitchen sink" install again, I'd reccomend reading the ref.*.php3 pages on php.net, just to be familiar with what is expected. > > > > FLAG: --with-xml=shared,/site/subsys/www/expat_1.1 \ > > > RESULT: > > > > Have to say, I've never seen =shared, passed before...no clue! > > I'll experiment with rebuilding without the shared argument being > present, and see what happens. > Well, I am not an auto(conf|make) guy, so I don't know...did you ever experiment with this? So, just to recap: the only thing missing is xml support, and aspell, which for the time being is N/A? Is this correct? --Joey Smith Please forgive the long sig: *** Notice To Bulk Emailers: Attention! Pursuant to US Code, Title 47, Chapter 5, Subchapter II, 227, any & all unsolicited commercial e-mail sent to this address is subject to a download and archival fee in the amount of the $1500 US and copies will be forwarded to domain administrators. Emailing denotes acceptance of said terms!