Using the mmbuildgpl command to build the GPFS portability layer on Linux nodes

Starting with GPFS 4.1.0.4, you can use the mmbuildgpl command to simplify the build process.

To build the GPFS portability layer using mmbuildgpl, enter the following command:
/usr/lpp/mmfs/bin/mmbuildgpl

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, and only some of these nodes have a compiler available, you can build the kernel module on one node, then create an installable package that contains the binary module for ease of distribution.

If you choose to generate an installable package for portability layer binaries, perform the following additional step: 
/usr/lpp/mmfs/bin/mmbuildgpl --build-package
When the command finishes, it displays the location of the generated package as in the following examples:
Wrote: /root/rpmbuild/RPMS/x86_64/gpfs.gplbin-3.10.0-229.el7.x86_64-5.1.0-x.x86_64.rpm
or
Wrote: /tmp/deb/gpfs.gplbin-4.4.0-127-generic_5.1.0-x_amd64.deb
You can then copy the generated package to other machines for deployment. By default, the generated package can be deployed only to machines whose architecture, distribution level, Linux kernel, and IBM Spectrum Scale maintenance level are identical with those of the machine on which the gpfs.gplbin package was built. However, you can install the generated package on a machine with a different Linux kernel by setting the MM_INSTALL_ONLY environment variable before you install the generated package. If you install the gpfs.gplbin package, you do not need to install the gpfs.gpl package.
Note: During the package generation, temporary files are written to the /tmp/rpm or /tmp/deb directory, so be sure there is sufficient space available. By default, the generated package goes to /usr/src/packages/RPMS/<arch> for SUSE Linux Enterprise Server, /usr/src/redhat/RPMS/<arch> for Red Hat Enterprise Linux, and /tmp/deb for Ubuntu Linux.
Important:
  • The GPFS portability layer is specific to both the current kernel and the GPFS version. If either the kernel or the GPFS version changes, a new GPFS portability layer needs to be built.
  • Although operating system kernels might upgrade to a new version, they are not active until after a reboot. Thus, a GPFS portability layer for this new kernel must be built after a reboot of the operating system.
  • Before you install a new GPFS portability layer, make sure to uninstall the prior version of the GPFS portability layer first.