>Re: Good instruction for installing webserver using RPM and tar.gz files???
Don't. :-) >I'm pretty used to installing OpenSSL, Mod_SSL, Mcrypt, cURL, PHP and Apache >with all of them in tar.gz files. Now I'm experiementing it on the Linux >and mySQL. Never tried it on both Linux and mySQL before. Jeez, if you can get the SSL crap to install properly from tar.gz, why mess with RPM for PHP and MySQL?! :-) The problem with most PHP RPM installs is that you are stuck with the versions of the 108 third-party software that the RPM-maker may or may not have decided to include, and what they decided to include only has a 1 in 2^108 (about a zillion) odds in being what you actually *WANT* in your PHP. Of course, you can muck with source RPMs which is even worse that tarball in the first place... But ain't nothing more painful than trying to figure out which of the 10,000 mysql-devel RPMs you need to match the RPM of mysql that's been on your machine from the RedHat installer. Hours down the tube. >The tricky part I found is that some come in RPM. I am familar with >installing using RPM. But from my understanding, I would have to uninstall >the existing RPM software. The tricky part is to knit together RPMs and >tar.gz(s) for those software because they all depend on each other. For >example in order of installation .... > > 1) IBM DB2 (or mySQL) > 2) Mcrypt > 3) OpenSSL > 2) cURL --> (depend on OpenSSL) > 3) Mod_SSL --> (it depend on OpenSSL) > 4) PHP --> (depend on Mod_SSL, cURL, OpenSSL, Mcrypt & DB2) > 5) Apache --> 5th (it depend on Mod_SSL, OpenSSL, PHP) > >So, anyone know of good instruction on the website somewhere? It does not >have to be a complete instruction or a perfect instruction. Just something >that can give me some understanding before I start working it. Or should I >just use all tar.gz files instead? Like forget about the RPM stuffs. The >reason I'm posting this is becuase I realize that PHP can easily not work >with some softwares if it is not installed correctly. You know! Here's the thing: You *NEVER* now where some RPM maker decided to put their files. They might be in /usr/include or they might be in /usr/local/include or they might be in /etc or the might be in /usr/local/lib or... The list is endless. Basically, you're *BEST* bet is to try to avoid using the RPMs for stuff you expect to update any time soon (like, for the life of the machine) and use tarballs for that. If the RPMs are already install, try to uninstall them (after doing a backup, of course) then install from tarball. Even if it gets all screwed up, it's not *that* hard to figure out, usually. For example, if GD isn't working, look for *TWO* copies of libgd.so on your box: locate libgd.so Or even just *TWO* copies of the header files: locate gd.h If there's a copy both in /usr/include and /usr/local/include, one of them ain't supposed to be there. Figure out which one by comparing it to the one you compiled a couple minutes ago. Nuke the wrong one, along with all the files that came with it. Be careful not to nuke other files that *happen* to start with 'gd' (like 'gdbm.h') but be sure to get all the ones that conflict with the .h files in your current GD. (like 'gdfont.h') Detoxifying an RPM-ed install can be very rewarding and satisfying :-) YMMV -- Like Music? http://l-i-e.com/artists.htm -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
