On 2013/11/22 16:09, Chris Cappuccio wrote: > James Turner [ja...@calminferno.net] wrote: > > On Fri, Nov 22, 2013 at 03:50:25PM -0800, Chris Cappuccio wrote: > > > Does Freeswitch compile and run on OpenBSD? I thought it was already > > > done, but just noticed it isn't in the official ports tree yet. > > > > > > > There seems to be a port in openbsd-wip [0]. > > > > [0] > > https://github.com/jasperla/openbsd-wip/tree/master/telephony/freeswitch
...which says in UPDATE, "Builds on amd64. Coredumps and high load average." > I noticed that and also this: https://github.com/tbullock/freeswitch-openbsd > > http://tbullock.comlore.com/2013/03/freeswitch-on-openbsd.html > > Seems to me that the SQLite problem is resolved by simply using the freeswitch > version of it. > > Chris > I had a look at freeswitch before, and came to the conclusion that it was fairly pointless to add to ports. A few snippets from http://jira.freeswitch.org/browse/FS-353 ... <xxx1> short answer is that the sqlite in tree, is no longer sqlite <xxx1> its patched six ways from sunday, and I don't think the sqlite people wanted any of the changes upstream <@xxx2> bytologist: lets not <@xxx2> what we have isn't stock SQLITE either <@xxx2> you can't use system libs of anything we provide <@xxx2> it'll crash all over the freakin place <@xxx3> (...) and changes has been made that specifically are known to cause horrible instability and segfaults So we can't really use it with the libraries from ports, and some of those libraries from ports have patches which may well need applying to freeswitch's versions of them. (It's not as bad as it used to be; there were a bunch more patches in apr for thread-related things which aren't there any more). If someone is interested in getting freeswitch on OpenBSD I think the only way is to just work on usptream's distribution, get any patches needed from ports into their version, and forget about ports for it.. (I lost interested in freeswitch in the end, too much hassle to get it to work on OpenBSD, and in the meantime Asterisk release engineering got considerably better, even if it's still sometimes a pain to get bugs fixed there ..)
