<div dir="ltr">Thanks Tao. I ended up fixing the "<span style="font-family:arial,sans-serif;font-size:13px">CONFIG_LNET_MAX_PAYLOAD redefined" error by locally modifying Lustre configuration scripts because in an cloud environment I'm working with rebuilding the kernel is not an option. </span><div>
<span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Also, in case anyone is interested in building the Lustre client on Debian Wheezy with kernel </span><font face="arial, sans-serif">3.14-0.bpo.1-amd64, in addition to the above fix and the patch I mentioned in my first message I also had to apply this: <a href="http://review.whamcloud.com/#/c/10325">http://review.whamcloud.com/#/c/10325</a> to fix the following error: "lustre/llite/file.c:3545:24: error: invalid operands to binary == (have \u2018kuid_t\u2019 and \u2018int\u2019) </font><span style="font-family:arial,sans-serif">current_fsuid() == 0 && .." More info can be found here: </span><font face="arial, sans-serif"><a href="https://jira.hpdd.intel.com/browse/LU-5058">https://jira.hpdd.intel.com/browse/LU-5058</a></font></div>
<div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Now moving on to functional testing the client...</font></div><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif">Cheers,</font></div>
<div><font face="arial, sans-serif">Bartek</font></div><div><font face="arial, sans-serif"> </font></div><div class="gmail_extra"><br><div class="gmail_quote">2014-05-31 18:56 GMT+02:00 Peng Tao <span dir="ltr"><<a href="mailto:bergwolf@gmail.com" target="_blank">bergwolf@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Thu, May 29, 2014 at 6:15 PM, Bartek <<a href="mailto:bgrinning@gmail.com">bgrinning@gmail.com</a>> wrote:<br>
> Hello,<br>
><br>
> I'm trying to build Lustre client on Debian Wheezy with kernel<br>
> 3.14-0.bpo.1-amd64. Here are my build steps are:<br>
> sh ./autogen.sh<br>
> sudo ./configure --disable-server<br>
> sudo dpkg-buildpackage<br>
> sudo dpkg -i lustre-source_2.5.59.0-32-gb265903_all.deb<br>
> sudo m-a -t build lustre<br>
> I also patched debian/rules to: ./configure --disable-server<br>
> --disable-ldfiskfs<br>
><br>
> I'm aware of changes needed for latest kernels (3.12-14):<br>
> <a href="https://jira.hpdd.intel.com/browse/LU-4416" target="_blank">https://jira.hpdd.intel.com/browse/LU-4416</a><br>
> <a href="https://jira.hpdd.intel.com/browse/LU-4993" target="_blank">https://jira.hpdd.intel.com/browse/LU-4993</a><br>
><br>
> So far, I applied the shrinker patch locally:<br>
> <a href="http://review.whamcloud.com/#/c/9300" target="_blank">http://review.whamcloud.com/#/c/9300</a> and that allowed me to get past the<br>
> shrinker compilation error. But now I'm running into another error (error:<br>
> "CONFIG_LNET_MAX_PAYLOAD" redefined) for which I didn't find any mentions in<br>
> Jira:<br>
><br>
> ...<br>
> echo "#define LUSTRE_RELEASE 3.14_0.bpo.1_amd64_gb265903" >> tmpver<br>
> cmp -s ../lustre/include/lustre/lustre_build_version.h tmpver > tmpdiff 2><br>
> /dev/null && \<br>
> rm -f tmpver tmpdiff || \<br>
> mv -f tmpver ../lustre/include/lustre/lustre_build_version.h<br>
> make[5]: Leaving directory `/usr/src/modules/lustre/lustre'<br>
> /usr/bin/make CC="gcc" -C /lib/modules/3.14-0.bpo.1-amd64/build \<br>
> -f /usr/src/modules/lustre/build/Makefile<br>
> LUSTRE_LINUX_CONFIG=/lib/modules/3.14-0.bpo.1-amd64/build/.config \<br>
> LINUXINCLUDE='-I$(srctree)/arch/$(SRCARCH)/include<br>
> -I$(srctree)/arch/$(SRCARCH)/include/generated -Iinclude $(if<br>
> $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include)<br>
> -I$(srctree)/arch/$(SRCARCH)/include/uapi<br>
> -Iarch/$(SRCARCH)/include/generated/uapi -I$(srctree)/include/uapi<br>
> -Iinclude/generated/uapi -include<br>
> /lib/modules/3.14-0.bpo.1-amd64/source/include/linux/kconfig.h' \<br>
> M=/usr/src/modules/lustre -o tmp_include_depends -o scripts -o \<br>
> include/config/MARKER modules<br>
> make[5]: Entering directory `/usr/src/linux-headers-3.14-0.bpo.1-amd64'<br>
> CC [M] /usr/src/modules/lustre/libcfs/libcfs/linux/linux-tracefile.o<br>
> In file included from <command-line>:0:0:<br>
> /usr/src/modules/lustre/config.h:26:0: error: "CONFIG_LNET_MAX_PAYLOAD"<br>
> redefined [-Werror]<br>
> In file included from<br>
> /lib/modules/3.14-0.bpo.1-amd64/source/include/linux/kconfig.h:4:0,<br>
</div></div>It seems that you have enabled CONFIG_LUSTRE_FS in your local kernel<br>
config which would then define CONFIG_LNET_MAX_PAYLOAD on its own. The<br>
easy workaround is to disable in-kernel client in your kernel and<br>
rebuild.<br>
I am not sure if it makes sense to support such use case as there<br>
would be two sets of client modules for the same kernel.<br>
<br>
Cheers,<br>
Tao<br>
</blockquote></div><br></div></div>