From: ima.sudonim@verizon.net
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: problem building multiple kernels with correct version numbers
Date: Thu, 11 Dec 2003 07:48:33 -0500 [thread overview]
Message-ID: <547F5518-2BD8-11D8-B1FC-00039398B344@verizon.net> (raw)
Hi,
I am still relatively new at kernel builds, but I have done a google
search and tried to follow the process of: make distclean dep vmlinux
modules modules_install
I have source trees for:
2.4.20-8d,
2.4.22-2f,
2.4.23-pre5-ben0
Somehow the kernel version in the core Makefile is always: VERSION 2,
PATCHLEVEL 4, SUBLEVEL 23 EXTRAVERSION -pre5-ben0
When I try to run my prebuilt kernels, the kernelversion info (uname
-r) is 2.4.23-pre5-ben0
I can't update this value in the Makefile without it getting written
over from somewhere during the make dep vmlinux process.
i) Where should I put in the kernel source tree an explicit source
number for the kernel I'm building?
ii) Is there a tool to explicitly set a version string inside a vmlinux
kernel?
iii) originally, I was just copying configuration information by
copying .config files from one source directory to another and
rebuilding. Did I somehow copy kernel version information withit?
iv) is there an option inside make menuconfig to set the kernel's
version number?
v) when I do a make modules_install, must I already be running the
vmlinux kernel made for it? It seems to always copy to
/lib/modules/2.4.23-pre5-ben0
I was using Set version information on all module symbols in Loadable
module support. Could this have somehow set a kernel version file (if
such exists) somewhere?
Should I just erase all of my source trees and start over from scratch?
Do I need to be running a built kernel to run make_install to update
/lib/modules for the kernel I've just built?
I am using Yellowdog linux (ppc) 3.01
I do not subscribe to this forum due to heavy traffic but will watch it
from the website versions.
Thank you!
Ima
reply other threads:[~2003-12-11 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=547F5518-2BD8-11D8-B1FC-00039398B344@verizon.net \
--to=ima.sudonim@verizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).