From: Keith Owens <kaos@ocs.com.au>
To: "Fr d ric L. W. Meunier" <0@pervalidus.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: warning during make modules
Date: Tue, 12 Dec 2000 12:14:28 +1100 [thread overview]
Message-ID: <3350.976583668@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 11 Dec 2000 21:42:14 -0200." <20001211214214.B1245@pervalidus>
On Mon, 11 Dec 2000 21:42:14 -0200,
Fr d ric L . W . Meunier <0@pervalidus.net> wrote:
>Is this a 2.4.0 issue? Because I see the warnings on 2.2.18
>too, and also building alsa-driver. I use modutils 2.3.22.
>binutils 2.10.1.0.2. glibc 2.2.
The kernel is trying to fudge the section flags for .modinfo to prevent
.modinfo being loaded as part of a module. This works on older
toolchains, it even works on recent toolchains but now you get an
annoying warning. modutils >= 2.3.19 has special case code for
.modinfo so the kernel fudge is no longer required.
The 2.4 kernel will be patched to remove the warning in my next set of
module changes, probably 2.4.1. The 2.2 kernel will _not_ be patched
because that would force all 2.2 users to upgrade their user space
tools which is a no-no for 2.2. But if you have already upgraded your
user space tools, you can patch 2.2 linux/module.h yourself to remove
the warning. Against 2.2.18-pre27.
Index: 18-pre27.1/include/linux/module.h
--- 18-pre27.1/include/linux/module.h Tue, 12 Sep 2000 13:37:17 +1100 kaos (linux-2.2/F/51_module.h 1.1.7.2 644)
+++ 18-pre27.1(w)/include/linux/module.h Tue, 12 Dec 2000 12:12:48 +1100 kaos (linux-2.2/F/51_module.h 1.1.7.2 644)
@@ -190,11 +190,6 @@ const char __module_parm_desc_##var[] \
__attribute__((section(".modinfo"))) = \
"parm_desc_" __MODULE_STRING(var) "=" desc
-/* The attributes of a section are set the first time the section is
- seen; we want .modinfo to not be allocated. */
-
-__asm__(".section .modinfo\n\t.previous");
-
/* Define the module variable, and usage macros. */
extern struct module __this_module;
-
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-12-12 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-11 23:42 warning during make modules Frédéric L . W . Meunier
2000-12-12 1:14 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-19 1:11 Linux 2.2.18pre22 Alan Cox
2000-11-19 10:07 ` Michael Marxmeier
2000-12-11 9:15 ` warning during make modules Corisen
2000-12-11 9:27 ` Keith Owens
2000-12-11 11:05 ` Corisen
2000-12-11 12:06 ` Keith Owens
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=3350.976583668@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=0@pervalidus.net \
--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