mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: jbglaw@lug-owl.de, akpm@osdl.org, torvalds@osdl.org
Subject: [PATCH 2.6.15-rc2-git6] Fix tar-pkg target
Date: Mon, 28 Nov 2005 18:04:15 +0100	[thread overview]
Message-ID: <20051128170414.GA10601@harddisk-recovery.nl> (raw)

Hi,

The various tar-pkg Makefile targets forget to apply the
CONFIG_LOCALVERSION_AUTO to the vminux and System.map files because the
script (scripts/package/buildtar) doesn't know about it. This can be
fixed by computing the correct "version" variable, but it's better to
use the one computed by Kbuild itself, just like the like the
"builddeb" and "mkspec" scripts do.

Without this patch, "make tar-pkg" would generate a file
linux-2.6.15-rc2.tar containing vmlinuz-2.6.15-rc2. With this patch, it
generates linux-2.6.15-rc2-g458af543.tar containing
vmlinuz-2.6.15-rc2-g458af543.


Erik

Signed-off-by: Erik Mouw <erik@harddisk-recovery.com>

diff --git a/scripts/package/buildtar b/scripts/package/buildtar
index d8fffe6..4c1b706 100644
--- a/scripts/package/buildtar
+++ b/scripts/package/buildtar
@@ -15,7 +15,7 @@ set -e
 #
 # Some variables and settings used throughout the script
 #
-version="${VERSION}.${PATCHLEVEL}.${SUBLEVEL}${EXTRAVERSION}${EXTRANAME}"
+version="${KERNELRELEASE}"
 tmpdir="${objtree}/tar-install"
 tarball="${objtree}/linux-${version}.tar"
 

             reply	other threads:[~2005-11-28 17:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28 17:04 Erik Mouw [this message]
2005-11-28 17:07 ` Jan-Benedict Glaw
2005-11-29 21:30 ` Andrew Morton
2005-11-29 20:36   ` Sam Ravnborg
2005-11-30  5:32     ` Brian Gerst
2005-11-30  9:05       ` Jan-Benedict Glaw
2005-11-30 12:03     ` Erik Mouw

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=20051128170414.GA10601@harddisk-recovery.nl \
    --to=erik@harddisk-recovery.com \
    --cc=akpm@osdl.org \
    --cc=jbglaw@lug-owl.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®