public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.de>
To: linux-kernel@vger.kernel.org
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	akpm@osdl.org
Subject: kbuild / KERNELRELEASE not rebuild correctly anymore
Date: Sun, 15 Jan 2006 10:51:14 +0100	[thread overview]
Message-ID: <200601151051.14827.rene@exactcode.de> (raw)

Hi all,

with at least 2.6.15-mm{2,3,4} untaring the kernel and running make menuconfig
(or most other favourite config tools) do not display a version anymore since
.kernelrelease it not build as dependecy.

I only noticed this because my build scripts grab the version before the build for
later file names on installations and leave this string empty after configuration of
latest linux kernels.

Sincerely,

-- 
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
            http://www.exactcode.de | http://www.t2-project.org
            +49 (0)30  255 897 45

             reply	other threads:[~2006-01-15  9:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15  9:51 René Rebe [this message]
2006-01-15 10:05 ` kbuild / KERNELRELEASE not rebuild correctly anymore Sam Ravnborg
2006-01-15 10:41   ` René Rebe
2006-01-15 11:19     ` Sam Ravnborg
2006-01-15 12:12       ` René Rebe
2006-01-15 12:31         ` Sam Ravnborg
2006-01-15 14:26           ` René Rebe
2006-01-15 23:29             ` Kyle Moffett
2006-01-16 11:15             ` [PATCH] kbuild: create .kernelrelease at *config step Sam Ravnborg
2006-01-15 10:13 ` kbuild / KERNELRELEASE not rebuild correctly anymore Grant Coady
2006-01-15 10:42   ` René Rebe

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=200601151051.14827.rene@exactcode.de \
    --to=rene@exactcode.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.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