Using the automatic configuration tool to build the GPFS portability layer on Linux nodes

To simplify the build process, GPFS™ provides an automatic configuration tool.

The following example shows the commands required to build the GPFS portability layer using the automatic configuration option (make Autoconfig):

cd /usr/lpp/mmfs/src
make Autoconfig
make World
make InstallImages

Start of change Each kernel module is specific to a Linux version and platform. If you have multiple nodes running exactly the same operating system level on the same platform, or if you have a compiler available on only one node, you can build the kernel module on one node, then create an RPM that contains the binary module for ease of distribution. End of change

If you choose to generate an RPM package for portability layer binaries, perform the following additional step:

make rpm

When the command finishes, it displays the location of the generated RPM:

<...Last line of output...>
Wrote:  /usr/src/redhat/RPMS/x86_64/gpfs.gplbin-2.6.18-128.1.14.e15-3.3.0-1.x86_64.rpm

You can then copy the generated RPM package to other machines for deployment. The generated RPM can only be deployed to machines with identical architecture, distribution level, Linux kernel, and GPFS maintenance level.

Note: During the package generation, temporary files are written to the /tmp/rpm directory, so be sure there is sufficient space available. By default, the generated RPM goes to /usr/src/packages/RPMS/<arch> for SUSE Linux Enterprise Server and /usr/src/redhat/RPMS/<arch> for Red Hat Enterprise Linux.