All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabian Fenaut <fabian.fenaut@free.fr>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Fabian Fenaut <fabian.fenaut@free.fr>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.4-mm1 and -mm2: include/linux/version.h missing (vanilla ok)
Date: Mon, 15 Mar 2004 19:04:23 +0100	[thread overview]
Message-ID: <4055F027.2070906@free.fr> (raw)
In-Reply-To: <20040315174148.GA2163@mars.ravnborg.org>

Sam Ravnborg wrote:

> On Mon, Mar 15, 2004 at 03:35:01PM +0100, Fabian Fenaut wrote:
> 
>> Why is there no include/linux/version.h after having compiled -mm1
>>  and -mm2 ? Compilation of kernel is fine, but because of this, my
>>  nvidia modules won't compile.
>> 
>> As said in the subject, 2.6.4 vanilla is ok, version.h is here 
>> after compilation.
>> 
>> I use debian woody, and I type
>> 
>> make-kpkg --append-to-version -ff --revision 1 binary-arch 
>> make-kpkg --append-to-version -ff --revision 1 modules_image
> 
> I dunno make-kpkg, but 'make clean' became a bit more effective in 
> mm1. So now 'make clean' deletes version.h - maybe that's your 
> problem?

I didn't run neither make-clean nor make-kpkg clean, and however,
version.h is not here, even just after the compilation of the kernel.

And, to compile my modules successfully, I copied version.h from vanilla
to /usr/src/2.6.4-mm2/include/linux (and modified it the correct way).
Then I compiled my modules, and after that, my hand-made version.h is
still here, so make-kpkg doesn't delete anything.

=> version.h is _never_ created.

Thank you for your help.

--
Fabian


  reply	other threads:[~2004-03-15 18:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 14:35 2.6.4-mm1 and -mm2: include/linux/version.h missing (vanilla ok) Fabian Fenaut
2004-03-15 17:41 ` Sam Ravnborg
2004-03-15 18:04   ` Fabian Fenaut [this message]
2004-03-15 18:43     ` Sam Ravnborg
2004-03-15 19:19       ` Fabian Fenaut

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=4055F027.2070906@free.fr \
    --to=fabian.fenaut@free.fr \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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.