From: Timur Tabi <ttabi@interactivesi.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>
Subject: Re: "couldn't find the kernel version the module was compiled for" - help!
Date: Tue, 14 Nov 2000 17:35:37 -0600 [thread overview]
Message-ID: <20001115000545Z129040-521+229@vger.kernel.org> (raw)
In-Reply-To: <11946.974244682@ocs3.ocs-net>
In-Reply-To: Your message of "Tue, 14 Nov 2000 15:58:38 MDT."<20001114222843Z131509-521+212@vger.kernel.org>
** Reply to message from Keith Owens <kaos@ocs.com.au> on Wed, 15 Nov 2000
10:31:22 +1100
> "#define __NO_VERSION__" must be in all but one of the sources that
> also include module.h. It suppresses the module_version string in
> module.h so it only make sense if the code includes module.h. But
> exactly one of the objects in a module must have a module_version
> string.
Ok, I made this change:
#ifndef __ENTRY_C__
#define __NO_VERSION__
#endif
#include <linux/version.h>
and in entry.c:
#define __ENTRY_C__
#include "include.h"
Unfortunately, it still doesn't work.
I tried "insmod -f tdmcddk.sys", but that didn't help either.
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please direct the reply to the mailing list only. Don't send another copy to me.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-15 0:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 21:58 "couldn't find the kernel version the module was compiled for" - help! Timur Tabi
2000-11-14 22:31 ` Steven Walter
2000-11-14 22:51 ` Timur Tabi
2000-11-14 23:31 ` Keith Owens
2000-11-14 23:35 ` Timur Tabi [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-14 23:41 Keith Owens
2000-11-14 23:44 ` Timur Tabi
2000-11-15 0:41 ` David Schleef
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=20001115000545Z129040-521+229@vger.kernel.org \
--to=ttabi@interactivesi.com \
--cc=kaos@ocs.com.au \
--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