Displaying 20 results from an estimated 90000 matches similar to: "Error compiling Dahdi: invalid use of undefined type struct module"
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
2008 Apr 01
2
cross compilation for ARM - ogg headers problem
Hi,
this problem seems to be coming up a lot lately -- the README.arm in
linphone tells people to remove libogg headers, but speexenc and
speexdec require them to build.
Perhaps we need a README.arm in libspeex telling people not to remove
the libogg headers.
K.
On 01/04/2008, Erwan A <mout551 at hotmail.fr> wrote:
>
> Hi all,
>
> I am following the README.arm from Simon
2008 Apr 01
5
cross compilation for ARM - ogg headers problem
On 01/04/2008, Erwan A <mout551 at hotmail.fr> wrote:
>
> Hi,
>
> Yes i agree with you. You don't have to delete these files.
>
> But if i cross compile with ogg header files, i have the following error :
>
>
> /usr/lib/libogg.so: could not read symbols: Invalid operation
> collect2: ld returned 1 exit status
> make[2]: *** [speexenc] Erreur 1
2008 Apr 01
2
problem with some ogg header files with speex
Hi all,
I am following the README.arm from Simon to cross compile linphone from my PC to an arm architecture. But i encounter problems about the ogg header.
I have this following error when i write this line :
./configure --prefix=/usr --host=arm-linux --with-gnu-ld --disable-static --enable-fixed-point --enable-arm-asm
the error is :
.
.
make[2]: entrant dans le r?pertoire ?
2008 Mar 28
2
speex - cross compil for ARM - problem ogg headers
Hi all,
I try to compile speex for ARM. I follow the README.arm and i always have the same errors :
make[2]: entrant dans le r?pertoire ? /usr/src/linphone/arm/speex-1.1.6/src ?
source='speexenc.c' object='speexenc.o' libtool=no \
depfile='.deps/speexenc.Po' tmpdepfile='.deps/speexenc.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
2008 Apr 01
0
cross compilation for ARM - ogg headers problem
Hi,
Yes i agree with you. You don't have to delete these files.
But if i cross compile with ogg header files, i have the following error :
/usr/lib/libogg.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[2]: *** [speexenc] Erreur 1
make[2]: quittant le r?pertoire ? /usr/src/linphone/arm/speex-1.1.6/src ?
make[1]: *** [all-recursive] Erreur 1
2008 Apr 01
0
cross compilation for ARM - ogg headers problem
Hi Conrad,
Thanks for your help.
I am unlucky. No i have this following error :
source='speexdec.c' object='speexdec.o' libtool=no \
depfile='.deps/speexdec.Po' tmpdepfile='.deps/speexdec.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
arm-linux-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../libspeex -I/usr/include -O2 -fno-exceptions -O2
2008 Apr 01
0
cross compilation for ARM - ogg headers problem
I think --without-libogg should do the trick, no? (though I haven't
actually tried it)
Jean-Marc
Conrad Parker a ?crit :
> On 01/04/2008, Erwan A <mout551 at hotmail.fr> wrote:
>> Hi,
>>
>> Yes i agree with you. You don't have to delete these files.
>>
>> But if i cross compile with ogg header files, i have the following error :
>>
2008 Apr 01
0
cross compilation for ARM - ogg headers problem
Hi all,
I am following the README.arm from Simon to cross compile linphone from my PC to an arm architecture. But i encounter problems about the ogg header.
I have this following error when i write this line :
./configure --prefix=/usr --host=arm-linux --with-gnu-ld --disable-static --enable-fixed-point --enable-arm-asm
the error is :
.
.
make[2]: entrant dans le r?pertoire ?
2008 Apr 01
2
cross compilation for ARM - ogg headers problem
IIRC, under ARM, I believe I was having issues with --without-libogg.
I resorted to just downloading libogg sources, setting up my
cross-compilation environment, and cross compiling it per the general build
directions (./configure, make, make install), then went back to building
speex -- everything worked like a charm for me then.
So -- Conrad. *Make sure* that you have libogg cross-compiled and
2011 May 04
1
Invalid use of undefined type when make dahdi
I am attempting to install Dahdi on a virtual machine running Centos 5.5 and having various problems.
yum install kernel-devel gcc make gcc-c++ libxml2-devel
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.optus.net
* extras: mirror.optus.net
* rpmforge: fr2.rpmfind.net
* updates: mirror.optus.net
Setting up Install Process
Package
2007 Jan 08
1
Cross-compilation of R and ld bug ?
Hello list,
I would like to cross-compile R packages using R 2.4.0. I am working on
Linux Debian and cross-compiled (windows binaries) without problems with
older R version.
I have used the doc of Yan and Rossini in the contributed section of the
R documentation (same version of MinGW...).
When I try to cross-compile R (make R), the procedure stopped and returns :
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
2008 Mar 25
1
speex - cross compil for ARM - problem ogg headers
Hi,
I try to compile speex for ARM. I follow the README.arm and i always have the same errors :
make[2]: entrant dans le r?pertoire ? /usr/src/linphone/arm/speex-1.1.6/src ?
source='speexenc.c' object='speexenc.o' libtool=no \
depfile='.deps/speexenc.Po' tmpdepfile='.deps/speexenc.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
arm-linux-gcc
2011 Feb 21
1
[Dahdi 2.4.0] DAHDI_CHANCONFIG failed on channel 1
Hello
On a brand new CentOS 5.5 host, I wanted to install Dahdi before
installing Asterisk 1.4.x.
So I untarred dahdi-linux-complete-2.4.0+2.4.0.tar.gz, followed by
make, make install, make config.
Next, I created the following files from scratch:
============ /etc/modprobe.d/dahdi.conf:
options wctdm opermode=FRANCE
============ /etc/dahdi/modules
wctdm
============ /etc/dahdi/system.conf
2011 Dec 21
1
dahdi: Unknown symbol kasprintf
When I compile dahdi I see these warnings:
WARNING: "kasprintf" [dahdi-linux-2.5.0.2/drivers/dahdi/wctdm24xxp/wctdm24xxp.ko] undefined!
WARNING: "kasprintf" [dahdi-linux-2.5.0.2/drivers/dahdi/dahdi.ko] undefined!
And "modinfo dahdi" shows that the driver was built for a 2.6.17 kernel, SMP mod_unload 586 4KSTACKS gcc-4.1
If I "modprobe -a dahdi", I get
2008 Apr 01
2
problem with some ogg header files with speex
Hi,
Thanks for your help.
It's true. I had to point files to the arm files. i have modified my command line by adding --with-ogg-libraries=/armbuild/lib/ . Here is the ogg.h file compiled for arm.
But now i have an other error :
source='speexdec.c' object='speexdec.o' libtool=no \
depfile='.deps/speexdec.Po' tmpdepfile='.deps/speexdec.TPo' \
2011 Jan 11
1
Issue with Red Alarm with DAhDi
Hi!
I have an analog line connected to my asterisk and when I try to answer a call I get this
-- Starting simple switch on 'DAHDI/7-1' -- Executing [s at from-pstn:1] Answer("DAHDI/7-1", "") in new stack -- Executing [s at from-pstn:2] Playback("DAHDI/7-1", "vm-intro") in new stack -- <DAHDI/7-1> Playing 'vm-intro' (language
2012 Apr 11
4
Dahdi-2.4.0+2.4.0 means ??
Hi,
can anyone tell me what does that 2.4.0+2.4.0 means in dahdi release
numbering ??? 2.4.0?????
regards
upendra.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20120411/9b160392/attachment.htm>
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