Subject: Re: [vserver] How to build kernel modules for host?
From: "Roderick A. Anderson" <raanders@acm.org>
Date: Tue, 09 Dec 2008 06:04:15 -0800

Herbert Poetzl wrote:
> On Wed, Dec 03, 2008 at 01:54:08AM +0100, erik pepermans wrote:
>> Hi,
>>  
>> Based on this asterisk subject, when I try to compile I get :
>>  
>> [root@ns dahdi-linux-2.0.0]# make KVER=2.6.22.19-vs2.3.0.34.1
>>
>> make -C /lib/modules/2.6.22.19-vs2.3.0.34.1/build ARCH=x86_64
>> SUBDIRS=/usr/src/dahdi-linux-2.0.0/drivers/dahdi
>> DAHDI_INCLUDE=/usr/src/dahdi-linux-2.0.0/include DAHDI_MODULES_EXTRA=" "
>> HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m
>> make[1]: Entering directory `/usr/src/kernels/2.6.22.19-vs2.3.0.34.1-x86_64'
>>  
>>   Building modules, stage 2.
>>   MODPOST 26 modules
>> WARNING: "rtc_register"
>> [/usr/src/dahdi-linux-2.0.0/drivers/dahdi/dahdi_dummy.ko] undefined!
> 					~~~~~~~~~~~~~~~~
> what is a 'dahdi'?
> 
> and why does it need a dummy module?

I'll jump in here as I'll be going down this road shortly.  Dahdi it the 
the replacement(rename) for zaptel in Asterisk.  It is used for timing 
of POTS and other telephony hardware/software.  The dummy module is 
needed for some additional Asterisk functionality even if there is no 
hardware involved.

I have built, but not tested, the zaptel dummy module.  A pain to build 
for the kernel non-guru ... to say the least.


Rod
-- 
> 
> best,
> Herbert
> 
>> WARNING: "rtc_unregister"
>> [/usr/src/dahdi-linux-2.0.0/drivers/dahdi/dahdi_dummy.ko] undefined!
>> WARNING: "rtc_control"
>> [/usr/src/dahdi-linux-2.0.0/drivers/dahdi/dahdi_dummy.ko] undefined!
>> make[1]: Leaving directory `/usr/src/kernels/2.6.22.19-vs2.3.0.34.1-x86_64'
>>
>> Is RTC built into the kernel by default ?
>>  
>> Brgds
>> Erik