Building the Native SP from SRPM Source Packages
Building from SRPM is like a source build, but much more automated and less prone to user error if you're less experienced at building from source. It also results in a set of packages you can install or upgrade easily across many machines.
The basic process to rebuild an SRPM is simply this command:
rpmbuild command, and others required for the build process, are often missing from a server installation, so you may need to install them first. The following list of packages covers most of the prerequisites on many systems:
stunnel (for curl-openssl)
You can save some time during the build process by installing all of the above that are available on your system, along with their dependencies. On "yum" platforms, the simplest way is just to install them all at once:
yum will just ignore any packages which aren't available or are already installed and will install any dependencies of the packages requested automatically. You'll discover any prerequisites not in the above list during the build process. The one exception to this is the
rpmbuild command itself. If that isn't installed by this point, you can use the "
yum provides rpmbuild" command to locate the package needed.
rpmbuild requires root access in order to use the default RPM tree in
/usr/src/redhat. This isn't recommended, but using a local RPM tree is beyond the scope of this document. Following the very small "Setup" section of How to patch and rebuild an RPM package will get you there in a few minutes, though.
To rebuild the whole set of packages required for the SP, you'll need to download the SRPMs from
the download site and save them to
You'll then need to repeat the same basic steps for each package, in the following order:
curl-openssl(on RHEL/CentOS 6.x and later)
If you jump ahead, the RPM commands will tell you what's missing. The basic steps for each package are:
Replace package, version, and arch above (usually
x86_64) with the necessary information in each case. Only some packages have a
schemas RPM you need to install.
If at any time, you're told that a package needed to build the next one is missing, simply install it using
yum or whatever tool is native to your OS. In particular, you'll usually need some kind of Apache development package (often
httpd-devel) and its dependencies, assuming your goal is to integrate with the Apache that comes with your OS.
If on the other hand something breaks, it's probably that you've found a bug in one of the packages (usually not in the source, just the packaging process) and you can search the mailing list or ask for help.
At the end of the process, you'll be left with everything you need installed and you can refer to the RPM topic to proceed.
A few options are built-in to control certain dependencies and turn on and off some optional features:
Don't include ADFS module
Expressly include the ODBC storage plugin (requires
Don't include the ODBC plugin, even if it can be built
Build against the original log4cpp library instead of log4shib
Include FastCGI support (requires
Bypass requirement for native OS httpd-devel package
Targeting a Custom Apache
Should the need arise to customize the build process to target a non-standard Apache, various options can be passed to the
rpmbuild command. In fact, you can completely control the
configure command used by defining the macro
In this fashion, you can supply the usual
configure options that control Apache build settings, such as
--with-apxs2 and so on.
If you need to disable the RPM's dependency on the native OS Apache development package, you can use the option for that listed above in the table.