From: Stuart Sheldon <stu@actusa.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: "make prepare" in 2.6.26.2 not behaving?
Date: Tue, 19 Aug 2008 13:11:27 -0700 [thread overview]
Message-ID: <48AB28EF.40608@actusa.net> (raw)
In-Reply-To: <20080819195228.GB6774@uranus.ravnborg.org>
Sam Ravnborg wrote:
> On Mon, Aug 18, 2008 at 08:41:59PM -0700, Stuart Sheldon wrote:
>> Hey all, think I found a little bug...
>>
>> I recently was attempting to build 3rd party modules on a 2.6.26.2
>> source tree after a "make clean" was run on the kernel source tree.
>>
>> In the past I would run "make oldconfig prepare scripts" and then build
>> and install the 3rd party module. All would work as expected.
>>
>> And all started well with the 2.6.26.2 tree. The module built without
>> error, but when I went to load it, it responded back with a version
>> error on the console, and the dmesg was: "no symbol version for
>> struct_module".
>>
>> If I rebuild the entire kernel and modules in the source tree and then
>> build the 3rd party module again, It builds and loads without issue.
>>
>> I'm hoping this is a bug, as I use the prepare method of setting up
>> source trees a lot. It saves me hours of time on my server farm.
>
> If you have MODULE_VERSIONING enabled then you need to build
> the kernel - "make prepare" is in that case not enough.
>
> Ig you have module.symvers around then that will do it.
>
> Sam
>
So the patch to delete the module.symvers from the tree exposed a
mistake in my config? Makes since. Just to clarify, I want
CONFIG_MODVERSIONS=n in my .config to use prepare? The help on the
setting seems to imply that turning it on makes the kernel less picky
about modules, but I guess I don't get it...
Will change that setting and test.
Thanks!
Stu
--
Randomly Generated Fortune Tag:
Many pages make a thick book.
prev parent reply other threads:[~2008-08-19 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 3:41 Stuart Sheldon
2008-08-19 19:52 ` Sam Ravnborg
2008-08-19 20:11 ` Stuart Sheldon [this message]
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=48AB28EF.40608@actusa.net \
--to=stu@actusa.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome