public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian-huber@web.de>
To: linux-kernel@vger.kernel.org
Subject: Re: modversion.h improvement suggestion
Date: Sun, 5 May 2002 18:36:34 +0200	[thread overview]
Message-ID: <E174Ozd-0007QI-00@smtp.web.de> (raw)
In-Reply-To: <Pine.GSO.4.05.10205051818350.20954-100000@mausmaki.cosy.sbg.ac.at>

On Sunday 05 May 2002 18:19, you wrote:
> On Sun, 5 May 2002, Sebastian Huber wrote:
> > Hello,
> > I tried to compile a device driver module and got the error that
> > 'modversion.h' cannot be found. My first questions were:
> > 	Are the include paths ok?
> > 	Do the maintainer now what he or she is doing?
> > 	Uses this driver code obsolete kernel stuff?
> > 	Has SuSE forgotten something to install?
> > Then I started a google search for 'modversion.h' and noticed that this
> > was a common problem. And after a while I found the solution ->
> > modversion.h is an automatically generated file.
> >
> > So what about a default modversion.h file:
> > /* This is an automatically generated file. Do not edit it. */
> > #error You have not generated the module versions. You have to ...
> >
> > This hint may save some time for those who are not so fit in kernel
> > issues.
>
> you should include module.h in any case - this also includes modversions.h
> (if you compile your kernel/module with MODVERSIONS enabled)
>
> 	++dent

They include modules.h, but if modversion.h doesn't exist you get of course 
the error that the file cannot be found. And if you don't play every day with 
the kernel this information alone don't help you very much. So an appropriate 
message might help you.

PS:
I'm not a member of this mailing list, so please cc me mails related to that 
subject.


       reply	other threads:[~2002-05-05 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.05.10205051818350.20954-100000@mausmaki.cosy.sbg.ac.at>
2002-05-05 16:36 ` Sebastian Huber [this message]
2002-05-05 16:00 modversion.h improvement suggestion Sebastian Huber
2002-05-05 23:43 ` Keith Owens
2002-05-06 21:03   ` Olaf Titz
2002-05-07  4:55     ` Keith Owens
2002-05-06 15:39 ` Alan Cox

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=E174Ozd-0007QI-00@smtp.web.de \
    --to=sebastian-huber@web.de \
    --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