Summary:	ASTERISK-08226: [patch] Zaptel trunk fail to compile / install on FreeBSD (6.1)
Reporter:	Paul Belanger (pabelanger)	Labels:
Date Opened:	2006-11-30 14:34:35.000-0600	Date Closed:	2007-01-16 14:40:20.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) compile_zaptel_on_freebsd.patch
Description:	Just like the title says Zaptel truck fails to compile on FreeBSD.  Looks like not much work has gone into porting it to BSD.  I'll start submitting some patches to get it to compile, then worry about testing functionality later. Thoughts?
Comments:	By: Tilghman Lesher (tilghman) 2006-11-30 14:42:48.000-0600 Is there a reason you aren't using the FreeBSD ports collection? By: Paul Belanger (pabelanger) 2006-11-30 14:55:01.000-0600 Curious to try the latest and greatest; I guess my only option is to use the ports (not really a problem). Quick question: Why not attempt to get the base drivers to compile and work on BSD rather then maintained via the ports? By: Paul Belanger (pabelanger) 2006-12-06 11:22:20.000-0600 Ok, need some help on this one, as I've never created a configure script before.  I can see in the asterisk-trunk/configure script we check for linux/soundcard.h and sys/soundcard.h.  However, in zaptel-trunk/configure script we only check for linux/soundcard.h.  Of course BSD its sys/soundcard.h, so I'm going to attempt to create a patch, but I'm pretty sure it will be ugly. FYI By: Paul Belanger (pabelanger) 2006-12-06 11:31:22.000-0600 My mistake, it looks like the zaptel/configure script does not even check to so if soundcard.h is available. By: Jason Parker (jparker) 2006-12-06 14:46:25.000-0600 The kernel interface on FreeBSD is different than on Linux..  I'm not sure what value there would be in making any of it compile.  Maybe I'm misunderstanding what you want to compile? By: Paul Belanger (pabelanger) 2006-12-06 15:18:52.000-0600 If anything, it would have it easier for us (BSD users) to port zaptel.  I understand Digium does not want to official support the OS, but if we can attempt to get parts of zaptel to compile out the box it would help greatly. IE: here is a patch to get the some of the zaptel binaries, not dependent on the kernel to compile. By: Jason Parker (jparker) 2006-12-06 15:23:03.000-0600 I guess that's a valid enough reason.  Essentially, you could cross-compile zaptel on a FreeBSD box as well. Do you have a disclaimer on file with Digium? By: Paul Belanger (pabelanger) 2006-12-06 15:26:22.000-0600 yes, must have forgot to check the Disclaimer on File checkbox. By: Kevin P. Fleming (kpfleming) 2006-12-11 12:40:31.000-0600 I don't understand; none of the actual hardware drivers are going to compile (let alone work) on FreeBSD at all. If you are referring to the userspace utilities, sure, it would be nice if they compiled on FreeBSD. However, since we have _never_ claimed to support any platform other than Linux with Zaptel, this cannot in any way be considered a major bug. By: Jason Parker (jparker) 2007-01-16 14:40:19.000-0600 I reviewed this patch and thought about it quite extensively, however, I don't believe we should include this into zaptel.  The FreeBSD port has already done all of this work, and are generally quick to port any major changes we add.