Re: Module problem around 1.3.60?
Aaron Ucko (UCKO@vax1.rockhurst.edu)
Tue, 27 Feb 1996 21:07:22 -0600 (CST)
>I noticed that somewhere around 1.3.60, insmod began to complain about
>static symbols included in a .o file that I'd try to load into the
>kernel. It was apparently treating them as if they were externals.
>For example, every .o file fails to load because "gcc2_compiled" is
>not defined (this is a static symbol added to every assembler file
>that gcc 2.x.y produces). I do not use KERNEL_MODVERSIONS. I have
>upgraded to the modules-1.3.57 package with no change. Modules
>used to work just fine and I've been assuming that this is some kind
>of obvious bug that would be fixed in the very next kernel release,
>but enough time has passed so that I really ought to mention it.
I'm pretty sure I read somewhere that this is a problem with HJ's latest
binutils release. (The fault is modules', but triggered by binutils.)
Either downgrade your binutils or ask Bjorn for his modules patch.
-- Aaron Ucko (ucko@vax1.rockhurst.edu; finger for PGP public key) | httyp!
"That's right," he said. "We're philosophers. We think, therefore we am."
-- Terry Pratchett, _Small Gods_ | Geek Code 3.1 [for explanation, finger
hayden@mankato.msus.edu]: GCS/M/S/C d- s: a18 C++(+++)>++++ UL++>++++ P++
L++>+++++ E- W(-) N++(+) o+ K- w--- O M@ V-(--) PS++(+++) PE- Y(+) PGP(+) t(+)
!5 X-- R(-) tv-@ b++(+++) DI+ !D-- G++(+++) e->+++++(*) h!>+ r-(--)>+++ y?