From: Keith Owens <kaos@ocs.com.au>
To: "kumar M" <kumarm4@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: exporting kernel symbols
Date: Tue, 29 Jan 2002 00:22:44 +1100 [thread overview]
Message-ID: <6909.1012224164@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 28 Jan 2002 13:13:38 -0000." <F127UjC2XxF6P0mCmg600006436@hotmail.com>
On Mon, 28 Jan 2002 13:13:38 +0000,
"kumar M" <kumarm4@hotmail.com> wrote:
>On a freshly installed RedHat 7.1 machine
>with 2.4.2-2 kernel, a 'make modules'
>throws up errors such as :
>----------------------------------------
>/usr/src/linux-2.4/include/linux/module.h:173: nondigits in number and not
>hexadecimal
>/usr/src/linux-2.4/include/linux/module.h:173: parse error before `62dada05'
>/usr/src/linux-2.4/include/linux/module.h:173:
>`inter_module_register_R_ver_str' declared as function returning a function
>/usr/src/linux-2.4/include/linux/module.h:173: warning: function declaration
>isn't a prototype
>.......................................................
>
>So we do a 'make mrproper' and 'make menuconfig' and
>save and exit without any changes to configuration.
>Then we rebuild the kernel.
>make dep & make modules are done smoothly.
>
>Can you let us know why we should be doing make mrproper
>on a system freshly installed with redhat 7.1(2.4.2-2smp)
RedHat do something strange with module symbols. I have never
understood what they are trying to do nor why it messes up a normal
kernel compile. Ask RH what the build procedure is for their
distributed kernels and why a normal build goes wrong.
next prev parent reply other threads:[~2002-01-28 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 13:13 kumar M
2002-01-28 13:22 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-13 21:10 Exporting Kernel Symbols shesha bhushan
2003-02-13 20:35 shesha bhushan
2003-02-13 20:22 shesha bhushan
2003-02-13 20:26 ` Randy.Dunlap
2002-01-27 15:16 exporting kernel symbols kumar M
2002-01-27 23:37 ` 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=6909.1012224164@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=kumarm4@hotmail.com \
--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
all inboxes | Powered by JetHome®