> -----Original Message----- > From: Stephen Rothwell [mailto:sfr@xxxxxxxxxxxxxxxx] > Sent: Wednesday, June 05, 2013 8:43 AM > To: Peng, Tao > Cc: Greg Kroah-Hartman; Andreas Dilger; linux-next@xxxxxxxxxxxxxxx; devel@xxxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH] staging/lustre: fix build errors > > Hi, > > On Tue, 4 Jun 2013 08:45:41 +0000 "Peng, Tao" <tao.peng@xxxxxxx> wrote: > > > > From 369398c782c914e5f0548d5bbad22c00c6b58b6a Mon Sep 17 00:00:00 2001 > > From: Peng Tao <bergwolf@xxxxxxxxx> > > Date: Tue, 4 Jun 2013 15:48:17 +0800 > > Subject: [PATCH] staging/lustre: fix build errors > > > > There are several issues: > > 1. set_cpus_allowed() is not available with CONFIG_CPUMASK_OFFSTACK on > > 2. CONFIG_MODULES may not be defined > > 3. CONFIG_MODULE_UNLOAD may not be defined > > > > Signed-off-by: Peng Tao <tao.peng@xxxxxxx> > > --- > > Stephen, please see if this fixes your build failure. I have tested it locally but only on X86 > architecture, with CONFIG_CPUMASK_OFFSTACK on and CONFIG_MODULES/CONFIG_MODULE_UNLOAD off. > > I have tried this with an x86_64 allmodconfig build and now I get just > this build problem: > > drivers/built-in.o: In function `crc32_pclmul_le_16': > (.text+0x28b9310): multiple definition of `crc32_pclmul_le_16' > arch/x86/built-in.o:(.text+0xe70d0): first defined here > We should really remove the crypto implementations inside Lustre code. I have a patch to do that and Andreas is helping review it. Once done, I will send it out. > BTW all the build problems I reported yesterday were with the x86_64 > allmodconfig build, my PowerPC build was fine (since it doesn't even try > to build the lustre code). > Thanks. With the crypto-removal patch, I can pass x86_64 allmodeconfig build. Will send out patches later. Best, Tao ��.n��������+%������w��{.n�����{��w����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
