i've seen this type of problem around, but I have hit a few snags. any help would be appreciated, but this is a fairly convoluted problem.

I am running Redhat 9. I want to upgrade my php to the latest version...or at least php version 4.3.11 (for security reasons). on a separate backup machine, i used the rpmbuild command to convert the latest tarball into an rpm, like is mentioned at other places in this site.

while building however, I got the error that my apache server was out-of-date (v.2.0.40), and needed to upgrade to at least apache 2.0.44. i am trying to make this a shared module, and configure it like '--with-apxs2=/usr/sbin/apxs'. when i upgraded to the recommended apache, the configure and build succeeds.

a source rpm is then created at the /src/usr/redhat/SRPMS folder entitled php-4.3.11.src.rpm.

the problems i have now are:

1) when I try to build/install the source rpm, no binary rpm appears at all. nothing shows up under the /src/usr/redhat/RPMS folder. could this be a problem with the original spec file? this is the first time I have tried to make a tarball an rpm, so maybe i am missing something basic here.

2) i had to upgrade apache above. on my production server, will i have upgrade apache on that machine? or can i just take this binary php rpm and install it with no apache upgrade? the 2.0.44 dependency only came up in the configure stage of building, after all.

Why build a .src.rpm at all? Why not go directly from tarball to binary .rpm with: rpmbuild -tb <filename>.spec?

Thanks for the reply. After trying the command rpmbuild -ta <tarball>, I get the error:

error: No compatible architectures found for build