similar to: dahdi 2.10.1 build fails

Displaying 20 results from an estimated 1000 matches similar to: "dahdi 2.10.1 build fails"

2015 Jun 01
1
dahdi 2.10.1 build fails
On 06/01/2015 04:49 PM, Shaun Ruffell wrote: > On Mon, Jun 01, 2015 at 04:24:31PM -0400, sean darcy wrote: >> On fedora 21, trying to build dahdi for kernel 4.0.4. >> >> gcc-4.9.2-6.fc21.x86_64 >> >> make -C /lib/modules/4.0.4-202.fc21.x86_64/build SUBDIRS=/home/asterisk/rpmbuild/BUILD/dahdi-linux-2.10.1/drivers/dahdi
2015 Jun 01
0
dahdi 2.10.1 build fails
On Mon, Jun 01, 2015 at 04:24:31PM -0400, sean darcy wrote: > On fedora 21, trying to build dahdi for kernel 4.0.4. > > gcc-4.9.2-6.fc21.x86_64 > > make -C /lib/modules/4.0.4-202.fc21.x86_64/build SUBDIRS=/home/asterisk/rpmbuild/BUILD/dahdi-linux-2.10.1/drivers/dahdi DAHDI_INCLUDE=/home/asterisk/rpmbuild/BUILD/dahdi-linux-2.10.1/include > DAHDI_MODULES_EXTRA=" "
2014 Jan 03
3
Problem building dahdi from source
Hello, I am getting the following error when compiling dahdi : make[2]: Entering directory `/usr/src/kernels/2.6.32-431.1.2.0.1.el6.x86_64' Building modules, stage 2. MODPOST 0 modules make[2]: Leaving directory `/usr/src/kernels/2.6.32-431.1.2.0.1.el6.x86_64' make -C /lib/modules/2.6.32-431.1.2.0.1.el6.x86_64/build
2015 Nov 13
3
Trying to compile DAHDI on Pidora 2014 (RPi)
I just purchased an Amfeltec USB-FXO adapter and am trying to compile DAHDI 2.10 on a Raspberry PI running Pidora 2014 R3. I have all the dependencies but I get an error and cannot finish. Is it even possible to compile DAHDI for the ARM plataform? Here is the error I am getting: root at astpi dahdi-linux-complete-2.10.2+2.10.2]# make make -C linux all make[1]: Entering directory
2013 Dec 02
1
Problems compiling dahdi modules
Hi, I am having the following issue after upgrading the kernel in a CentOS machine. [root at localhost dahdi-linux-complete-2.7.0.1+2.7.0.1]# make make -C linux all make[1]: Entering directory `/usr/src/dahdi-linux-complete-2.7.0.1+2.7.0.1/linux' make -C drivers/dahdi/firmware firmware-loaders make[2]: Entering directory
2017 Jul 30
2
dahdi kernel module
Does anyone know if there are any plans to update the dahdi-linux kernel module code? It no longer compiles with recent kernels, and the last release of dahdi-linux appears to have been around March of 2016. I am currently running 4.6.3-300.fc24.x86_64 (on a Fedora system obviously) and the dahdi-linux-complete-2.11.1+2.11.1 release builds and runs under this kernel, but if I try to build it under
2013 Jun 10
1
DAHDI-linux 2.7 compile error with CONFIG_DAHDI_NET enabled
Not sure how I should officially report this, but I'm getting a compile error with DAHDI-linux 2.7 when I define CONFIG_DAHDI_NET in include/dahdi/dahdi_config.h. I am able to compile successfully when I leave it undefined, but I need to be able to use the network support. <snipped> /oct6100_api/oct6100_tsst.o AR /tmp/dahdi-linux-2.7.0-net/drivers/dahdi/oct612x/lib.a
2009 Mar 17
2
DAHDI or Zaptel doesn't compile against 1.4.24
Hi, We installed the latest 1.4.24 on a test machine and can't get zaptel nor dahdi compile. It's a Linux Debian Etch. Errors we have: keewi:/usr/src/dahdi-linux-2.1.0.4# make make -C /lib/modules/2.6.18-custom.2/build ARCH=i386 SUBDIRS=/usr/src/dahdi-linux-2.1.0.4/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-2.1.0.4/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes
2009 Nov 13
2
openSuse 11.2 and dahdi-linux
OK, I know it's only just out today but this is what I get when compiling dahdi-linux. make -C drivers/dahdi/firmware firmware-loaders make[1]: Entering directory `/usr/src/dahdi-linux-2.2.0.2/drivers/dahdi/firmware' make[1]: Leaving directory `/usr/src/dahdi-linux-2.2.0.2/drivers/dahdi/firmware' make -C /lib/modules/2.6.31.5-0.1-default/build
2014 Jun 13
1
dahdi-linux 2.6.2 failing to compile with linux 3.13
Hello, I'm getting the following errors when compiling dahdi-linux 2.6.2 under Ubuntu 14.04 with kernel 3.13.0-24-generic. I did google and found one thread suggesting the errors should be fixed in 2.6.2, and another suggesting to try 2.4 which didn't make sense but I tried anyway, and it gave similar warnings. Would anyone know how to make it compile? Thanks in advance. make[1]:
2011 Aug 07
2
Dahdi does not build against Kernel 3.0.0
Errors follow: make make -C linux all make[1]: Entering directory `/usr/local/src/asterisk/dahdi-linux-complete-2.4.1.2+2.4.1/linux' make -C drivers/dahdi/firmware firmware-loaders make[2]: Entering directory `/usr/local/src/asterisk/dahdi-linux-complete-2.4.1.2+2.4.1/linux/drivers/dahdi/firmware' make[2]: Leaving directory
2010 May 27
1
Meetmee user introduction disabled
I updated Asterisk to 1.6.2.7 and now the user introduction in the meetme application is no longer working: [May 27 09:26:51] WARNING[2407]: channel.c:4034 ast_request: No channel type registered for 'DAHDI' -- Created MeetMe conference 1023 for conference '800' [May 27 09:26:51] WARNING[2407]: app_meetme.c:3640 find_conf: No DAHDI channel available for conference, user
2011 Jan 31
1
Error compiling Dahdi: invalid use of undefined type struct module
All, I'm installing Asterisk with Dahdi on a server with a custom kernel compile. I've got the kernel source in /lib/modules/2.6.34.6-xxxx-grs-ipv6-64/build which points to /usr/src/linux-headers-2.6.34.6 and I think that's fine, but am getting all these "struct module" errors. Can anyone advise? Thanks! # make make -C drivers/dahdi/firmware firmware-loaders make[1]:
2009 Jan 03
1
OSLEC
Hello oslec make error on RHEL 2.6.9 : Warning: could not find versions for .tmp_versions/dahdi.mod Warning: could not find versions for .tmp_versions/xpd_fxo.mod Warning: could not find versions for .tmp_versions/xpd_fxs.mod Warning: could not find versions for .tmp_versions/xpd_pri.mod Warning: could not find versions for .tmp_versions/xpp.mod Warning: could not find versions for
2009 Mar 18
0
[Fwd: Re: DAHDI or Zaptel doesn't compile against 1.4.24]
Tzafrir Cohen a ?crit : > On Tue, Mar 17, 2009 at 07:16:26PM +0100, Administrator TOOTAI wrote: > >> Hi, >> >> We installed the latest 1.4.24 on a test machine and can't get zaptel >> nor dahdi compile. It's a Linux Debian Etch. Errors we have: >> >> keewi:/usr/src/dahdi-linux-2.1.0.4# make >> make -C /lib/modules/2.6.18-custom.2/build
2009 May 15
0
howto build oslec with dahdi-linux-2.1.0.4 or svn?
On Fedora 11, gcc-4.4, I'm trying to build oslec in dahdi-linux, but: [asterisk at asterisk dahdi-linux]$ make make -C drivers/dahdi/firmware firmware-loaders make[1]: Entering directory `/home/asterisk/build/dahdi/svn/dahdi-linux/drivers/dahdi/firmware' make[1]: Leaving directory `/home/asterisk/build/dahdi/svn/dahdi-linux/drivers/dahdi/firmware' make -C
2009 Feb 23
0
Can't compile Dahdi on SuSE 10.1/Kernel 2.6.16.54-0.2.5-smp/GCC 4.1.2
Below is the output when the compile fails. any suggestions? make -C /lib/modules/2.6.16.54-0.2.5-smp/build ARCH=i386 SUBDIRS=/usr/src/dahdi-linux-2.1.0.4/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi-linux-2.1.0.4/include DAHDI_MODULES_EXTRA=" " HOTPLUG_FIRMWARE=yes modules DAHDI_BUILD_ALL=m make[1]: Entering directory `/usr/src/linux-2.6.16.54-0.2.5-obj/i386/smp' make -C
2013 Feb 15
2
dahdi-linux dahdi-tools and libpri/libpri-
hello , i try to install dahdi-linux/dahdi-linux-current.tar.gz ,dahdi-tools/dahdi-tools-current.tar.gz and libpri/libpri-1.4-current.tar.gz but got these error msg make -C drivers/dahdi/firmware firmware-loaders make[1]: Entering directory `/usr/src/dahdi-linux-2.6.1/drivers/dahdi/firmware' make[1]: Leaving directory `/usr/src/dahdi-linux-2.6.1/drivers/dahdi/firmware' make -C
2015 Nov 04
2
Re: P2V conversion failed with "/run/lvm/lvmetad.socket: connect failed: No such file or directory"
Hi Richard, Thanks for your response, We have followed the steps mentioned in https://www.redhat.com/archives/libguestfs/2015-November/msg00015.html Now we are able to connect the V2V Conversion Server from Physical server after booting from livecd. Once ssh connection established, "Start Conversion" opens up another UI which has necessary info. of hardware (eg. CPU, RAM, HDD
2010 Apr 26
1
Dahdi will not compile on Unbuntu Studio Linux 9.10 (Karmic) 32bit
Been trying to get this to go but nongo :-). I'm asking for some guidance especially if I should not be doing this on an RT kernel. I've installed what is supposed to be all of the requred deps. Some factors that may be adding to my problem are: 1. this is only a test.. it's a 32bit guest OS running in VMware under a 64 bit windows host.. (although I'be compiled it on other