For Zaptel developpers regarding compilation problem on FC5


like some (many ?) people I have had problems compiling zaptel on a Fedora core 5 system, kernel 2.6.15-1.2054.

Error was as follow :

[quote]make[1]: Entering directory /usr/src/kernels/2.6.15-1.2054_FC5-smp-i686' CC [M] /root/install_asterisk_1.4/zaptel-1.4.0-beta1/wcusb.o /root/install_asterisk_1.4/zaptel-1.4.0-beta1/wcusb.c:1451: error: unknown field owner specified in initializer /root/install_asterisk_1.4/zaptel-1.4.0-beta1/wcusb.c:1451: warning: initialization from incompatible pointer type make[2]: *** [/root/install_asterisk_1.4/zaptel-1.4.0-beta1/wcusb.o] Error 1 make[1]: *** [_module_/root/install_asterisk_1.4/zaptel-1.4.0-beta1] Error 2 make[1]: Leaving directory/usr/src/kernels/2.6.15-1.2054_FC5-smp-i686’
make: *** [linux26] Error 2

An easy workaround was to comment or delete references to owner in wcusb.c [1451] and xpp_usb.c [430].

After some searches on, I found that usb_driver.owner disappeared in kernel 2.6.15, not 2.6.16, so it seems to me that the compilation problem could easily be avoided by changing :



in wcusb.c and xpp_usb.c.

I know for sure that you are much more aware of these problems than I am, and maybe my suggestion is completely wrong, nevertheless it solves the problem on FC5 and seems coherent with what I found regarding kernel changes…

Thanks for your excellent work :wink:


The steps are:-

  1. Find the cpu type u r runing using uname :
    uname -m

  2. Download the both the kernel and kernel-devel rpms having similar version and corresponding to your cpu or m/c type (smp or plain).

  3. Install by updating the existing package:
    rpm -Uvh [package]

  4. Immediately after installing you will find that
    uname -v
    returns the previous kernel version.
    This gives you hint that the system needs to be restarted.

  5. Before restarting check that your grub.conf has the updated kernel details.
    It usually has it but this is just for not getting any kernel panic or any other panics.

  6. After restarting see if the kernel version has changed. ‘uname -v’ should reflect the updated
    Kernel version.

  7. Now you can make zaptel

Question… I recall that I had to comment out those lines to make the zaptel compile propperly…

Is it possible to go back and re-do so it will compile without those errors?

And what specifically is the function of that pariticular area of codding for the zaptel drivers?