Chad Albert wrote: > I am trying to compile wanpipe on current ports and FreeBSD 7.1-RELEASE. > During build I get the error below. Has anyone else encountered this or know > how to get past it. I tried Sangoma and even though they list FreeBSD as a > supported operating system they will not support it and have told me I need > to move to Linux. I am using Sangoma A102 2 port E1/T1 cards. If anyone has > a T1 card they get better support out of I would love input as well. > > > > Compile error: > -----8<-------8<---------8<----------8< > In file included from > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel.h:36, > from sdla_tdmv.c:36: > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:35: error: > conflicting types for 'atomic_t' > ../../include/wanpipe_defines.h:970: error: previous declaration of 'atomic_t' > was here > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:66: error: > conflicting types for 'change_bit' > /sys/gnu/fs/ext2fs/i386-bitops.h:63: error: previous definition of > 'change_bit' > was here > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:75: error: > conflicting types for 'clear_bit' > /sys/gnu/fs/ext2fs/i386-bitops.h:53: error: previous definition of 'clear_bit' > was here > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:81: error: > conflicting types for 'set_bit' > /sys/gnu/fs/ext2fs/i386-bitops.h:43: error: previous definition of 'set_bit' > was > here > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:87: error: > conflicting types for 'test_bit' > /sys/gnu/fs/ext2fs/i386-bitops.h:77: error: previous definition of 'test_bit' > was here > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:93: error: > conflicting types for 'find_first_zero_bit' > /sys/gnu/fs/ext2fs/i386-bitops.h:90: error: previous definition of > 'find_first_zero_bit' was here > In file included from > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel.h:36, > from sdla_tdmv.c:36: > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:169:1: warning: > "MOD_DEC_USE_COUNT" redefined > In file included from sdla_tdmv.c:32: > ../../include/wanpipe_common.h:260:1: warning: this is the location of the > previous definition > In file included from > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel.h:36, > from sdla_tdmv.c:36: > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel-compat.h:170:1: warning: > "MOD_INC_USE_COUNT" redefined > In file included from sdla_tdmv.c:32: > ../../include/wanpipe_common.h:259:1: warning: this is the location of the > previous definition > sdla_tdmv.c:95: error: conflicting types for '__zt_mulaw' > /usr/ports/misc/zaptel/work/zaptel-bsd/zaptel/zaptel.h:1791: error: previous > declaration of '__zt_mulaw' was here > *** Error code 1 > > Stop in /usr/ports/misc/wanpipe/work/wanpipe-3.3.1/sources/wanpipe. > *** Error code 1 > > Stop in /usr/ports/misc/wanpipe/work/wanpipe-3.3.1/sources. > *** Error code 1 > > Stop in /usr/ports/misc/wanpipe/work/wanpipe-3.3.1. > *** Error code 1 > > Stop in /usr/ports/misc/wanpipe. > *** Error code 1 > > Stop in /usr/ports/misc/wanpipe. > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > Asterisk-BSD mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-bsd > This fails because zaptel 1.4.11(vr?) doesn't work right.
Alex, the freebsd support person at Sangoma, is the person responsible for this afaik--he has been made aware of the workaround for this situation. Sangoma has also been made aware of false advertising on their website on multiple occasions. I'll leave to you to decide what that means about the company. I know if I had a choice now, I'd ditch my Sangoma products in heartbeat. The workaround around I've found is to just use http://www.oldports.org/ to put a previous version of zaptel on which wanpipe will compile against(1.4.6_7 maybe?). Another thing to consider is if asterisk will work properly with the version of zaptel you've got installed so be aware of that too. Also wanpipe works perfectly under fbsd7 when done correctly contrary to Sangoma documentation. When I first got started with asterisk on freebsd, I went with sangoma because they did provide freebsd support. Ironically, digum cards are probably much better supported now than Sangoma. I think there are a couple of other voice tdm asterisk freebsd compatible cards, but not sure what they are. At the end of the day, my FreeBSD/Asterisk experience has been good, my Sangoma not so good. My Sangoma card are a101d and a104d. Another funny experience with them is I got my first card, an a101, then call in about it a month later only to hear from them that it wasn't supported either. Had to send it back and pay for upgrade to A101d. -- Adam Vandemore Systems Administrator IMED Mobility (605) 498-1610 _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- Asterisk-BSD mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-bsd
