[asterisk-users] dahdi-linux 2.1.0.4 released

[Shaun Ruffell]

Mr. James W. Laferriere wrote:
> On Tue, 3 Feb 2009, Shaun Ruffell wrote:
>> Thomas Kenyon wrote:
>>> I can't get this to build, the following error is produced:
>>>
>>>   CC [M]
>>> /usr/src/asterisk/1.6/dahdi-linux-2.1.0.4/drivers/dahdi/xpp/xproto.o
>>> /usr/src/asterisk/1.6/dahdi-linux-2.1.0.4/drivers/dahdi/xpp/xproto.c: In
>>> function 'xproto_get':
>>> /usr/src/asterisk/1.6/dahdi-linux-2.1.0.4/drivers/dahdi/xpp/xproto.c:96:
>>> error: implicit declaration of function 'module_refcount'
>>> make[3]: ***
>>> [/usr/src/asterisk/1.6/dahdi-linux-2.1.0.4/drivers/dahdi/xpp/xproto.o]
>>> Error 1
>>> make[2]: ***
>>> [/usr/src/asterisk/1.6/dahdi-linux-2.1.0.4/drivers/dahdi/xpp] Error 2
>>> make[1]: ***
>>> [_module_/usr/src/asterisk/1.6/dahdi-linux-2.1.0.4/drivers/dahdi] Error 2
>>> make[1]: Leaving directory `/usr/src/linux-2.6.28'
>>> make: *** [modules] Error 2
>>>
>>>
>>> This is on a P4 machine with gcc-4.1.2, (mot sure what else to include
>>> really, DAHDI Tools 2.1.0.2, asterisk 1.6.0.3).
>>>
>>> TIA for any help.
>> is CONFIG_MODULE_UNLOAD defined in your kernel config?
> 
>  	And why should this be a build time issue for DAHDI ?  Just a "?" .

It shouldn't be, but the module_refcount function is only defined by 
kernels that allow module unloading.  But that explains why we never saw 
this error in any of our testing because we primarily test with default 
kernel configs, both for vanilla kernels and some standard distributions.