asterisk users - Nov 2008 - Problem with DAHDI and OSLEC integration.

Hi List.
I've bought a new server for my home asterisk installation and I'm
trying to install asterisk with dahdi drivers and OSLEC. To do that I've
got the svn dahdi-linux trunk revision 5366 and the echo subproject from
the 2.6.28-rc6 Linux kernel sources.
As reported in the dadhi README file I've uncommented out the two OSLEC
related lines at Kbuild file in the dahdi-linux/drivers/dahdi folder.
I don't know if there is a bug in the Kbuild trunk revision or if I did
something wrong, but I was not able to successfully build the
dahdi_echocan_oslec.ko until I've changed the line:

obj-m += ../staging/echo/

with

obj-m += ../staging/echo/echo.o

With the original one I got some warning messages about oslec symbols
not defined. I think that the builder was not able to find the oslec
object file.

Am I doing something wrong?

Thank you and best regards.
Marco Signorini

>Am I doing something wrong?
I just posted this exact issue on Wednesday:
http://lists.digium.com/pipermail/asterisk-users/2008-November/222063.html

I never got any response and Digium came through with keys for my HPEC
license in the nick of time. I am not pleased with the admin overhead
HPEC requires and want to use oslec so I am keen on a resolution here
as well. If you come up with anything, due tell.

jlc

On Sun, Nov 23, 2008 at 11:44:04PM +0100, Marco Signorini
wrote:
> Hi List.
> I've bought a new server for my home asterisk installation and I'm
> trying to install asterisk with dahdi drivers and OSLEC. To do that
I've
> got the svn dahdi-linux trunk revision 5366 and the echo subproject from
> the 2.6.28-rc6 Linux kernel sources.
> As reported in the dadhi README file I've uncommented out the two OSLEC
> related lines at Kbuild file in the dahdi-linux/drivers/dahdi folder.
> I don't know if there is a bug in the Kbuild trunk revision or if I did
> something wrong, but I was not able to successfully build the
> dahdi_echocan_oslec.ko until I've changed the line:
> 
> obj-m += ../staging/echo/
> 
> with
> 
> obj-m += ../staging/echo/echo.o
> 
> With the original one I got some warning messages about oslec symbols
> not defined. I think that the builder was not able to find the oslec
> object file.
> 
> Am I doing something wrong?
Have you copied there the files from the directory drivers/staging/echo
in a recent (that is: >= 2.6.28-rc1) kernel tree?

(Anybody with a quick command to grab just that directory without
getting the full kernel tree?)

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir