From: Andi Kleen <ak@muc.de>
To: Albert Kajakas <Albert.Kajakas@mail.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3rdparty modules for 2.5.53
Date: 01 Jan 2003 19:56:11 +0100 [thread overview]
Message-ID: <m3isx8em2c.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <200301011719.h01HJOB21702@mail-fe2.tele2.ee>
Albert Kajakas <Albert.Kajakas@mail.ee> writes:
> Hello!
> I have a problem with compiling modules for 2.5.
I recently tracked down the same problem.
Add a -DKBUILD_MODNAME="yourname" compile option to one of the files,
the new loader requires a module name section. It should be only set
once for each module.
In addition make sure you're using the new style module_init/module_exit
macros instead of init_module/cleanup_module.
-Andi
P.S.: I agree that the error reporting sucks for this one. It would
be better if the kernel loader give some kind of text message back.
next prev parent reply other threads:[~2003-01-01 18:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 17:19 3rdparty modules for 2.5.53 Albert Kajakas
2003-01-01 18:24 ` Sam Ravnborg
2003-01-01 18:56 ` Andi Kleen [this message]
2003-01-01 22:29 ` Bjoern A. Zeeb
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 22:32 Albert Kajakas
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=m3isx8em2c.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=Albert.Kajakas@mail.ee \
--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 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.