[asterisk-bugs] [Zaptel 0012787]: Compile problem on Kernel 2.6.16 series on x86_64 architecture

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12787 
====================================================================== 
Reported By:                netmax
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   12787
Category:                   wcte12xp
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     new
Zaptel Version:             1.4.11 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-04-2008 15:58 CDT
Last Modified:              06-05-2008 09:16 CDT
====================================================================== 
Summary:                    Compile problem on Kernel 2.6.16 series on x86_64
architecture
Description: 
I can't compile zaptel on 2.6.16.x kernels on x86_64 architecture.
The last working zaptel version was 2.4.7.1.

The distributions where this happens are:
SuSE Linux Enterprise 10
SuSE Linux 10.1

The i386 architecture compiles and works fine.

If you need additional information, please let me now. I'll try to help
as much as i can.
====================================================================== 

---------------------------------------------------------------------- 
 sruffell - 06-05-08 09:16  
---------------------------------------------------------------------- 
Thanks for the output.

It appears like an int is passed to spin_lock_irqsave instead of a long. 
I've uploaded 12787-1.patch against zaptel 1.4.11 for you to try to see if
that is truly what the issue is on your system. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-05-08 09:16  sruffell       Note Added: 0087842                          
======================================================================