From: Patrick Farrell <paf@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] CentOS 6 - Build problems with kmod
Date: Fri, 19 Aug 2016 16:10:05 -0500 [thread overview]
Message-ID: <57B775AD.6060600@cray.com> (raw)
In-Reply-To: <665d003f-24fa-66c3-a713-4e8587623b8c@llnl.gov>
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
>
next prev parent reply other threads:[~2016-08-19 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 20:00 [lustre-devel] CentOS 6 - Build problems with kmod Patrick Farrell
2016-08-18 20:43 ` Christopher J. Morrone
2016-08-18 20:44 ` Christopher J. Morrone
2016-08-18 22:11 ` Patrick Farrell
2016-08-19 13:57 ` Ben Evans
2016-08-19 15:27 ` Patrick Farrell
2016-08-19 16:41 ` Patrick Farrell
2016-08-19 17:03 ` James Simmons
2016-08-19 17:29 ` Ben Evans
2016-08-19 20:52 ` Christopher J. Morrone
2016-08-19 20:44 ` Christopher J. Morrone
2016-08-19 20:51 ` Patrick Farrell
2016-08-19 20:58 ` Christopher J. Morrone
2016-08-19 21:10 ` Patrick Farrell [this message]
2016-08-19 21:25 ` Christopher J. Morrone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57B775AD.6060600@cray.com \
--to=paf@cray.com \
--cc=lustre-devel@lists.lustre.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.