The workaround for the client build is in the first comment of that ticket, i.e.:


rpmbuild --rebuild --define 'lustre_name lustre-client' --define 'configure_args --disable-server' lustre-client-2.4.0-2.6.32_358.6.2.el6.x86_64_gd3f91c4.src.rpm


if rebuilding from the SRPM, or:


./configure --enable-client --disable-server


if using a checkout of the Git repository. The issue was only related to rebuilding the clients and is a minor one that only requires that the --disable-server flag be introduced alongside the --enable-client flag. Previously, only the --enable-client flag was required.


While that ticket refers to the 2.6.32_358.6.2.el6.x86_64, the method is the same for other kernel versions. That does not necessarily mean that Lustre has been verified to run on other kernel releases, however. The changelog typically lists the support matrix for a Lustre release:









Malcolm Cowe, Systems Engineer

Intel High Performance Data Division


+61 408 573 001


From: hpdd-discuss-bounces@lists.01.org [mailto:hpdd-discuss-bounces@lists.01.org] On Behalf Of Arman Khalatyan
Sent: Tuesday, July 09, 2013 7:54 PM
To: hpdd-discuss@lists.01.org
Subject: [HPDD-discuss] Are there some workaround rebuilding lustre 2.4 on SL6.4?



I have seen bug report on rebuild:

I wondered if some one can advice a workaround for rebuilding lustre 2.4 on SL6.4 with kernel 2.6.32-358.11.1.el6.x86_64.

Thank you