All of lore.kernel.org
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.de>
To: Grant Coady <gcoady@gmail.com>
Cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Roman Zippel <zippel@linux-m68k.org>,
	akpm@osdl.org
Subject: Re: kbuild / KERNELRELEASE not rebuild correctly anymore
Date: Sun, 15 Jan 2006 11:42:16 +0100	[thread overview]
Message-ID: <200601151142.16256.rene@exactcode.de> (raw)
In-Reply-To: <eb0e02f40601150213g4589820csfc508f4ba2271cb4@mail.gmail.com>

Hi,

On Sunday 15 January 2006 11:13, Grant Coady wrote:
> On 1/15/06, René Rebe <rene@exactcode.de> wrote:
> > 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.
>
> grant@sempro:~/linux/linux-2.6.15-mm4a$ cat .kernelrelease
> 2.6.15-mm4a
>
> Works for me ;)

After a build? Yes. But before? E.g. at make menuconfig time or thereafter?

Yours,

-- 
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 10:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15  9:51 kbuild / KERNELRELEASE not rebuild correctly anymore René Rebe
2006-01-15 10:05 ` 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 [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=200601151142.16256.rene@exactcode.de \
    --to=rene@exactcode.de \
    --cc=akpm@osdl.org \
    --cc=gcoady@gmail.com \
    --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 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.