Personally, I'd recommend compiling from source it is at all possible. 
You'll likely get improved performance, and it's nice to know you can set 
things up exactly as you see fit.

Another thing you could try if that seems daunting or you need to install 
the RPMs onto several machines that all have the same set up (serverS, 
right?) would be to grab a source RPM and rebuild it on one machine. 
Basically, a command like this should work:

# rpm --rebuild php-x.x.x.src.rpm

The RPM should unbundle, configure, and compile, install itself, then place 
a fresh RPM in /src/redhat/RPMS/something (depending on your architecture). 
The new RPM will install on any system that has the same setup and 
libraries as the one you just performed the rebuild on.

In some cases, there may be times when you'll need to edit a file or two in 
the RPM to get it to compile. There should be howtos on this at 


Darren Gamble wrote:

> Good day,
> This isn't strictly a PHP question, but, I am hoping someone on this list
> has gone through this already and can provide some assistance.
> I'd like to upgrade to PHP 4.1.1 on our Redhat 7.2 servers, and so I've
> downloaded all of the PHP RPMs from Rawhide.  I would really, really like
> to do this with RPMs if at all possible.
> When I go to install, I find out that:
> error: failed dependencies:
>   is needed by php-4.1.1-1
> OK, no problem so far.  I just need to get the new openssl packages.
> But, after downloading them and adding them to the install list, I then
> find that (which would be replaced by is
> needed by
> dozens of packages on the system.  I really can't upgrade them all.
> I am just going from openssl-0.9.6b-8 to openssl-0.9.6c-2 .  It appears to
> me that openssl must have changed the API for their library between an
> extremely minor version number (is that even supposed to happen?), which
> is what I think is causing me the problem.
> I'm not quite sure how to proceed.  Has anyone else on the list done this
> yet?
> Thanks to all who reply,

PHP General Mailing List (
To unsubscribe, visit:

Reply via email to