From: Keith Owens <kaos@ocs.com.au>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel/module compiler version problem
Date: Sun, 13 Jun 2004 16:34:07 +1000 [thread overview]
Message-ID: <29225.1087108447@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 11 Jun 2004 15:16:00 -0400." <40CA04F0.9000307@nortelnetworks.com>
On Fri, 11 Jun 2004 15:16:00 -0400,
Chris Friesen <cfriesen@nortelnetworks.com> wrote:
>I'm running 2.4.22, build with gcc 3.3.1, modutils 2.4.22.
>
>I have an ATM driver that is shipped with a binary blob and a source code shim.
> It compiles fine. When I go to load it, I get the following error:
>
>"The module you are trying to load is compiled with a gcc
>version 2 compiler, while the kernel you are running is compiled with
>a gcc version 3 compiler. This is known to not work."
>
>Presumably the binary blob was compiled with gcc 2.x? Is there any way to
>override this? "insmod -f" doesn't seem to work.
That patch originally came from RedHat, and was included in modutils
2.4.22. From RH Bugzilla 73732.
"The insmod in Red Hat Linux 8.0 looks for modules and kernels which do
not have a matching gcc version. This is done because both the base and
the Red Hat kernel ABI for gcc 2 and gcc 3 built kernels are not the
same. This is due to workarounds for old (egcs) compiler bugs which
change the padding in kernel data structures.
Other vendors using gcc 3 series compilers received many strange bug
reports that turned out to be gcc 2 and gcc 3 module mixups. We saw the
same problems and verified the cause in our earlier beta releases. In
order to assist our customers Red Hat extended insmod to detect the
problem case and display an error message."
prev parent reply other threads:[~2004-06-13 6:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 19:16 kernel/module compiler version problem Chris Friesen
2004-06-11 19:31 ` Greg KH
2004-06-11 19:52 ` Chris Friesen
2004-06-11 19:38 ` Richard B. Johnson
2004-06-11 19:59 ` Chris Friesen
2004-06-13 6:34 ` Keith Owens [this message]
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=29225.1087108447@ocs3.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=cfriesen@nortelnetworks.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