[asterisk-bugs] [Zaptel 0009633]: Unable to build loadable kernel module on 2.4.18-19.7.x

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9633 
====================================================================== 
Reported By:                valley
Assigned To:                qwell
====================================================================== 
Project:                    Zaptel
Issue ID:                   9633
Category:                   wcfxo
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Zaptel Version:             1.4.2  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             04-30-2007 01:20 CDT
Last Modified:              07-31-2007 14:52 CDT
====================================================================== 
Summary:                    Unable to build loadable kernel module on
2.4.18-19.7.x
Description: 
I get this error

# modprobe zaptel
/lib/modules/2.4.18-19.7.x/misc/zaptel.o: couldn't find the kernel version
the module was compiled for
# modprobe ztdummy
/lib/modules/2.4.18-19.7.x/misc/zaptel.o: couldn't find the kernel version
the module was compiled for


after compiling zaptel 1.4.2.1 under 2.4.18-19.7.x kernel, gcc (GCC)
3.4.1, GNU Make 3.81. (A patched up RedHat 7.3.)  Same problem with all 1.4
releases since 1.4.0.

After lots of tinkering, Google led me to this article
http://www.linuxdocs.org/HOWTOs/Module-HOWTO/x150.html in Module Howto,
that says: "What insmod is telling you is that it looked in usbcore.o for a
piece of information any legitimate LKM would have -- the kernel version
with which the LKM was intended to be used -- and it didn't find it. We
know now that the reason it didn't find it is that the file isn't an LKM."

Indeed, whereas a successfully compiled 1.2.x zaptel.o contains sections
indicating, e.g., kernel_version=2.4.18-19.7.x., the object file compiled
from zaptel 1.4.x doesn't.

This means that zaptel 1.4.x release can't make an LKM under my system.
====================================================================== 

---------------------------------------------------------------------- 
 qwell - 07-31-07 14:52  
---------------------------------------------------------------------- 
I'm going to go ahead and close this.

You're running a distro that was released more than 5 years ago, and
you've made significant modifications to it (ie; upgrading gcc).

If you can reproduce this on something newer, we'd be more than happy to
reopen this bug. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-31-07 14:52  qwell          Status                   new => resolved     
07-31-07 14:52  qwell          Resolution               open => won't fix   
07-31-07 14:52  qwell          Assigned To               => qwell           
07-31-07 14:52  qwell          Note Added: 0068158                          
======================================================================