Bristuff-0.4.0-RC4-xr7
I am following the guide here:
http://updates.xorcom.com/astribank/bristuff/1.4/bristuff-current/INSTALL.html for installing bristuff on a CentOS5.11 box (stock 2.6.18-398.el5.i686). Whilst building zaptel I get the error as follows:
CC [M]
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/card_bri.o In file included from
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/xpd.h:26,
from
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/card_bri.c:29:
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/xdefs.h:157:
error: conflicting types for ‘bool’
include/linux/types.h:36: error: previous declaration of ‘bool’ was here In file included from
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/xpd.h:31,
from
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/card_bri.c:29:
include/linux/device.h:407: error: expected identifier or ‘(’ before ‘const’
make[4]: ***
[/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/card_bri.o]
Error 1
make[3]: ***
[/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp]
Error 2
make[2]: ***
[_module_/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel]
Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.18-398.el5-i686′
make[1]: *** [modules] Error 2
make[1]: Leaving directory
`/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649′
make: *** [all] Error 2
Can anyone help please? Thanks in advance.
3 thoughts on - Bristuff-0.4.0-RC4-xr7
Err… what would you do that?
Bristuff (and anything Zaptel) is left for the record and historical value. But there’s practically nothing useful there. I wouldn’t waste my time on it.
That said,
Yeah, see how this is resolved in later versions of DAHDI. Or just remove that typedef of bool. If it’s provided by the kernel, DAHDI
doesn’t need to provide it.
—
Tzafrir Cohen icq#16849755 jabber:tzafrir.cohen@xorcom.com
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com http://www.xorcom.com
—
Thanks for your response. As far as I can see I have no choice but use Zaptel as that is downloaded as part of the bristuff script. If there is a better way of getting a HFC PCI card to play nicely with Asterisk please let me know 🙂
There are two entries that refer to “typedef int bool;”, see excerpt of /usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/xdefs.h below:
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,19) /* Also don't define this for later RHEL >= 5.2 . hex_asc is from the
* same linux-2.6-net-infrastructure-updates-to-mac80211-iwl4965.patch
* as is the bool typedef. */
#if LINUX_VERSION_CODE != KERNEL_VERSION(2,6,18) || ! defined(hex_asc)
typedef int bool;
#endif
#endif
#else typedef int bool;
#endif typedef struct xbus xbus_t;
typedef struct xpd xpd_t;
typedef struct xframe xframe_t;
typedef struct xpacket xpacket_t;
typedef struct xops xops_t;
typedef __u32 xpp_line_t; /* at most 31 lines for E1
*/
typedef byte lineno_t;
typedef byte xportno_t;
#define PORT_BROADCAST 255
#endif /* XDEFS_H */
Removing those gives me the following error:
In file included from
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/xpd.h:31,
from
/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/card_bri.c:29:
include/linux/device.h:407: error: expected identifier or ‘(’ before ‘const’
make[4]: ***
[/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp/card_bri.o]
Error 1
make[3]: ***
[/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel/xpp]
Error 2
make[2]: ***
[_module_/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649/kernel]
Error 2
make[2]: Leaving directory `/usr/src/kernels/2.6.18-398.el5-i686′
make[1]: *** [modules] Error 2
make[1]: Leaving directory
`/usr/src/bristuff-0.4.0-RC4-xr7/zaptel-1.4.12.9.svn.r4649′
make: *** [all] Error 2
Can someone advise what I am missing?
[snip]
The HFC based Asterisk B410P and Hx8 + B400M cards are supported by DAHDI. If you use something with a HFC-S chip then you can use the sources below which add support for HFC-S to DAHDI. Note that they may not use the latest DAHDI version so you may have to figure out a way to get the patches applied to current DAHDI. The one time I tried the dahdi-hfcs stuff it seemed to work fine (very light usage only).
http://sourceforge.net/projects/dahdi-hfcs/
http://www.openvox.cn/pub/drivers/dahdi-linux-complete/
HTH, Patrick