From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Farrell Date: Fri, 19 Aug 2016 16:10:05 -0500 Subject: [lustre-devel] CentOS 6 - Build problems with kmod In-Reply-To: <665d003f-24fa-66c3-a713-4e8587623b8c@llnl.gov> References: <9957200e-17fe-2b8d-ad99-e8dfb5019f12@llnl.gov> <88922ad0-ba51-f28f-b062-69b2bcfafa16@llnl.gov> <17c61f0e-5835-b14a-2c56-6dbe01dcdca5@llnl.gov> <57B77146.6010201@cray.com> <665d003f-24fa-66c3-a713-4e8587623b8c@llnl.gov> Message-ID: <57B775AD.6060600@cray.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lustre-devel@lists.lustre.org On 08/19/2016 03:58 PM, Christopher J. Morrone wrote: > On 08/19/2016 01:51 PM, Patrick Farrell wrote: >> On 08/19/2016 03:44 PM, Christopher J. Morrone wrote: >>> On 08/18/2016 03:11 PM, Patrick Farrell wrote: >>>> Chris, >>>> >>>> >>>> I agree with your contention about the kernel symbols, that's why I >>>> rebuilt from scratch and reinstalled. Just did it again. Still getting >>>> the error. >>>> >>>> >>>>> It sounds like you built your own kernel. Did you install all the >>>>> resulting kernel packages before building lustre (including any >>>>> devel-related packages)? >>>> Yes, but this process doesn't produce anything other than the kernel >>>> RPM. >>> You are saying that literally only one rpm is produced? If that isn't >>> what your are saying, please list all of the produced rpms, and also >>> list which ones you are installing. >> Yes, one non-source RPM. I don't install any RPMs as part of the build >> process itself. > You should be installing RPMs as part of the build process. You should > install Lustre's BuildRequires before building Lustre. Huh. OK. I have never needed to do so before when building everything from scratch. Is this build process documented somewhere, so I can switch to it in my testing environment? I don't know how to invoke a CentOS kernel build to create those RPMs I now need. > >>> If you only have a single kernel rpm, then you almost certainly don't >>> have the correct packages installed to allow Lustre to compile against >>> that kernel. Lustre is probably compiling against some other installed >>> kernel. >> It's compiling the whole kernel from source, so I don't need any other >> packages. I build Lustre against the kernel bits directly, in the >> directories where they were built, not by installing any kernel RPMs. > That is only going to work if you don't want to make lustre RPM > packages. If you want to build RPM packages, you need to follow > standard RPM practices. In other words, you need to have Lustre's > prerequite packages installed before you build Lustre's RPMs. > > So you are going to need to those other kernel packages, and you need to > install them before building Lustre. Funnily enough, I've been building Lustre RPM packages this way for years, and they've always worked fine. I get that it's not standard practice and I need to adjust - But it did work up until now, and I believe it's the only documented process for building Lustre and the kernel from source. - Patrick > > Chris >