Jonathan Hilgeman wrote: > You must be kidding me. FreeBSD 4.x and PHP 4.x were made for each other. > Installation is simplicity itself. Just go to your shell, type in: > > cd /usr/ports/www/mod_php4 > make install
WOW... I mean OOPS! How did I miss this one?! ...I just got done looking in the /usr/ports/www/mod_php4 - yikes! Boy do feel dopey. :-\ One question tho. Do you know wheather this will break my current *open*ssl apache? I happen to notice that your description below indicates *mod*ssl. This is a bit important, as I'm a CA and I've already gotten/ built all the necessairy files for it. Thank you *very* much for the update* -- Chris > > > You'll be presented with a menu where you can check off the modules you want > to install. I can send you a written guide if you want. That's the biggest > advantage of FreeBSD - the ports system. I can take a absolutely blank box, > put FreeBSD 4.4 on it, and have Apache 1.3.20+Mod_SSL+Mod_PHP4+Mod_Perl > running on it with MySQL 3.23.42 and cURL 7.8.2 all working within 4 hours, > and most of that is just waiting for packages to be downloaded or files > copied over somewhere. Understood - why do you think I'm using it ;-) > > > - Jonathan > > -----Original Message----- > From: Chris [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 15, 2001 8:31 AM > To: [EMAIL PROTECTED] > Subject: [PHP-INST] ANNOUNCE-PHP4.x not supported on FreeBSD platform > Importance: High > > Greetings, > After 12hrs. of attempting to configure>make>install PHP-4.0.4pl1 or > php-4.0.6. on > a FreeBSD 4.3 machine. I have concluded that it *is* not and *was* not > intended to > be used on this platform. This comes after reading any and all the > documentation I > could find, reading and subscribing to the install and gen groups. > reading the majority > of the news archive. Attempting to implement possible suggestions found > there. > I have used (as the last attempt) the following configure syntax (from > config.nice): > # Created by configure > > "./configure" \ > "--with-apxs=/usr/local/sbin/apxs" \ > "--enable-versioning" \ > "--with-mysql=/usr/local/include/mysql" \ > "--enable-track-vars" \ > "--with-openssl=/usr/include/openssl" \ > "--with-gettext" \ > "--with-imap-ssl" \ > "--with-imap" \ > "--disable-posix" \ > > As you can see, I already have apache installed (openSSL version). Also > have MySQL > already installed and functioning. Also gettext installed and working. > However, the *only* > time configure completed was when I *didn't* use the =PATH to all but > apache-apxs. Which > led to the warning that if I wanted to have ssl support that I should > install it first. :-\ > So, I proceded to delete *all* the files in the php-4.0.x dir and untar > another fresh copy > re-configure, it puked which led to: can't find Open SSL <evp.h>. I have > tried *many* other > variations of the path statements. But all lead to the same message! The > file in question *is* > there; /usr/include/openssl/evp.h. So what kind of braindead configure > script is this?! Sorry, > but after struggling with it for this many hours, you might imagine my > frustration. > > Thanks to *any* and *all* who might take the time to help. > Sincerely, > Frustrated > > -- > PHP Install Mailing List (http://www.php.net/) > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > To contact the list administrators, e-mail: [EMAIL PROTECTED] -- Chris out... _________ __________ __________ _____________ / _____/\ / ____ \ / ______/\ /____ ____/\ / /\____\/ / /\_ / /\ / / \____\/ \___/ /\___\/ / /_/__ / /_/_/ / / / /__/_ / / / / _____/\ / ____ / / \_____ \ / / / / /\____\/ / /\_ / / / \____\ /\ / / / / / / / / / / / / _________/ / / / / / /___/ / /___/ / /___/ / /___________/ / /___/ / \___\/ \___\/ \___\/ \___________\/ \___\/.dnswatch.com ....................................... . Isn't it apropriate Micro$oft chose . . the name Windows - . . Glass being so fragile and all. . ....................................... -- PHP Install Mailing List (http://www.php.net/) To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
