From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>, bj0rn@blox.se
Subject: kernel/module compiler version problem
Date: Fri, 11 Jun 2004 15:16:00 -0400 [thread overview]
Message-ID: <40CA04F0.9000307@nortelnetworks.com> (raw)
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.
Thanks,
Chris
next reply other threads:[~2004-06-11 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 19:16 Chris Friesen [this message]
2004-06-11 19:31 ` kernel/module compiler version problem 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
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=40CA04F0.9000307@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=bj0rn@blox.se \
--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