From: Stuart Sheldon <stu@actusa.net>
To: linux-kernel@vger.kernel.org
Subject: "make prepare" in 2.6.26.2 not behaving?
Date: Mon, 18 Aug 2008 20:41:59 -0700 [thread overview]
Message-ID: <48AA4107.9090009@actusa.net> (raw)
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.
Thanks in advance for listening,
Stuart Sheldon
next reply other threads:[~2008-08-19 3:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 3:41 Stuart Sheldon [this message]
2008-08-19 19:52 ` "make prepare" in 2.6.26.2 not behaving? Sam Ravnborg
2008-08-19 20:11 ` Stuart Sheldon
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=48AA4107.9090009@actusa.net \
--to=stu@actusa.net \
--cc=linux-kernel@vger.kernel.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.