[asterisk-users] dahdi-linux 2.1.0.4 released

Shaun Ruffell sruffell at digium.com
Tue Feb 3 16:10:01 CST 2009


Thomas Kenyon wrote:
> 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?
>>
> No, does it need to be for building them then?
> 

It shouldn't, but the module_refcount function is only defined in 
kernels that are configured to allow module unloading.  This probably 
needs a mantis issue to make sure the drivers build when the kernel is 
not configured to allow modules to unload.




More information about the asterisk-users mailing list