[App_rpt-users] Anyone compiling asterisk from sources on Debian.

[Tom Russo]

I'm getting started on a project that will ultimately use
asterisk/app_rpt to handle a repeater linking system in a fairly
complex set-up.  For the moment I have a simple proof-of-concept
project before me, but because it's ultimately going to be a big,
non-allstarlink project I really don't want to use ACID or anything
other pre-packaged system that's meant to be turn-key for a simple
set-up.

I'm much more familiar with Debian-based systems than with
Fedora/RH/CentOS systems, and so I would rather use that as the base.
 I've got Debian Squeeze (the current stable system) installed on an
otherwise empty machine, have pulled the files.tar.gz file from the
place where ACID's installer would have downloaded it, and have
installed all the dependencies (libraries, dev packages for them,
kernel headers, etc.).  But right now I'm encountering Issues building
the Zaptel kernel module that I don't quite get.  Is anyone here using
the app_rpt sources of Asterisk on a Debian system who might be able
to help me diagnose what's going wrong with my build?

The short story is that the zaptel kernel module build is behaving
very much like it's not getting the kernel headers right, even though
the correct headers for the kernel are installed.  It doesn't complain
about not finding specific files, though, it's merely dying during
compilation of pciradio.c with undefined macros that are definitely
present in kernel headers that it should have found.  I don't want to
burden the list with details unless there is interest in the solution,
though.  If someone else is using app_rpt on a Debian-based system,
I'd love to be in contact to hash out details.

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 http://kevan.org/brain.cgi?DDTNM
 "The truth will set you free, but first it will piss you off."