[asterisk-dev] Dahdi-tools cross-compiling problem

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sat Sep 26 09:28:01 CDT 2009


On Fri, Sep 25, 2009 at 06:20:59PM -0300, Raphael Amorim wrote:
> Hello All,
> 
> I've successfully built dahdi-linux for my embedded ppc enviroment, but I'm
> having
> some trouble trying to compile dahdi-tools. I'm using LTIB to organize my
> BSP and
> I'm getting the following error on .configure:
> 
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking minix/config.h usability... no
> checking minix/config.h presence... no
> checking for minix/config.h... no
> checking whether it is safe to define __EXTENSIONS__... yes
> checking sys/soundcard.h usability... yes
> checking sys/soundcard.h presence... yes
> checking for sys/soundcard.h... yes
> checking linux/soundcard.h usability... yes
> checking linux/soundcard.h presence... yes
> checking for linux/soundcard.h... yes
> checking for gcc... (cached) gcc
> checking whether we are using the GNU C compiler... (cached) yes
> checking whether gcc accepts -g... (cached) yes
> checking for gcc option to accept ISO C89... (cached) none needed
> checking how to run the C preprocessor... gcc -E
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking for GNU make... make
> checking for grep... (cached) /bin/grep
> checking for sh... /bin/bash
> checking for ln... /bin/ln
> checking for wget... /usr/bin/wget
> checking for -Wdeclaration-after-statement support... yes
> checking for DAHDI_CODE in dahdi/user.h... no
> checking for newtBell in -lnewt... no
> checking for usb_init in -lusb... no
> checking for GENERIC_HDLC_VERSION version 4 in linux/hdlc.h... no
> checking for GENERIC_HDLC_VERSION version 4 in linux/hdlc/ioctl.h... yes
> configure: ***
> configure: *** Building this package requires DAHDI support. ***
> configure: *** Please install the dahdi-linux package. ***
> configure: ***

Alternatively, dahdi-tools merely need <dahdi/user.h> from dahdi-linux. 
This is already present in the installation. So all you need to do is:

  ./configure --with-dahdi=path/to/dahdi-linux

See, for instance, the script build_tools/live_dahdi in dahdi-linux .

Note that while this is likely to work in the future, it is not
guaranteed 100% to workand remains somewhat of a workaround. Installing
dahdi-linux to your target tree should be better.

-- 
               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



More information about the asterisk-dev mailing list