Minq-Wei directed me to the snapshot at http://devs.callweaver.org/ trunk_snapshots/ which is already bootstrapped. I was able to build callweaver-1.1.99.20070423 successfully! Thanks Ming-Wei.
And after installing all translations of sounds to gsm,ulaw,alaw and sln (didn't try less than all yet) i was able to place my first call to echo test, then to myself which i didn't answer and then to voicemail. There are a few little sporadic ticking noises i hear. Seems like only playing into my softphone since the voicemail attachment that came to my email inbox telling me i had a message, when played, had no tick sounds in it. Any thoughts on eliminating the clicks, or where i can go to read up on what that is about? Thank you all who have made this possible and to those who guided me with enough info to get me up and running. So i would like to help in some fashion, if at least to be another Mac OS X tester. In that light, i have composed a list of issues that remain for me at this point. This list has nothing in it about learning extensions and dialplan stuff -- totally another story. Issues on building callweaver with Mac OS X 10.4.8 and in general: 1. bootstrap.sh fails on Mac OS X since it can't find libtoolize. What is libtoolize? must use bootstrapped package instead for now, currently available here: http://devs.callweaver.org/trunk_snapshots/ -- UPDATE: Paul writes today: > I downloaded and compiled the latest versions of automake (1.6.3), > autoconf (2.61) and libtool (1.5.22) from the GNU ftp site (they > install > in /usr/local/ by default). > > Ran bootstrap.sh and it went through with a few warnings but no > showstoppers. > > Ran configure and make all with no problems so it is possible. But Ivan has problems with automake 1.9.6 and says: > When I run bootstrap on my MacBook Pro, it complains about version > mismatch: > > ..... > configure.ac:53: version mismatch. This is Automake 1.9.6, > configure.ac:53: but the definition used by this AM_INIT_AUTOMAKE > configure.ac:53: comes from Automake 1.9. You should recreate > configure.ac:53: aclocal.m4 with aclocal and run automake again. > running autoheader in libltdl ... > running autoconf in libltdl ... > ERROR: failed to generate Makefile.in > Ivan-C-Myrvolds-MacBook:~/Documents/CallWeaver/callweaver.trunk > imyrvold$ 2. sounds dir is hard to find. I had to dig around to find where to put the sounds on installing. Perhaps layout.xxx files should have it specified in there. It is called opbxsoundsdir and is defined as $ {opbxdatadir}/sounds in the Makefile, and opbxdatadir is (in the layout.xxxx files) defined as ${prefix}/share/callweaver, at least for FreeBSD layouts which it looks like the configure is using. How does a layout get specified? 3. which sounds to use on Mac OS X? I co'ed callweaver-sounds trunk, found the tools directory in my local working copy and ran 'convert2' to get ulaw, alaw, gsm ans sln for each file. Then i copied the whole thing to the sound dir. Have yet to test which ones are needed at a minimum. I think Ming-Wei said ulaw or alaw should work on non-linux. If i have more than one, which does it use? 4. sox needs to be installed on Mac OS X. Maybe other systems? You can get it from here: http://sox.sourceforge.net/ -- It build on Mac OS X 10.4.8 just fine. 5. would like to have a simpler directory layout for Mac OS X/darwin. I propose something more like the one that was used in openpbx.org from RC3. Can this be specified at configure time? Here is layout.bsd modified to something more flat (could call layout.simple): opbxprefix=/usr/local opbxexecdir=${prefix}/libexec opbxutilsdir=${prefix}/sbin opbxconfdir=${prefix}/etc opbxlibdir=${prefix}/lib/ opbxvardir=${prefix}/var opbxdatadir=${prefix}/share/data opbxlogdir=${prefix}/var/log opbxrundir=${prefix}/var/run opbxspooldir=${prefix}/var/spool opbxmandir=${prefix}/share/man opbxdocdir=${prefix}/share/doc Peace, Dan On Apr 23, 2007, at 8:21 PM, CtRiX wrote: > Daniel Melnechuk wrote: >> Hi all, >> Well looks like i have minimum version level as required in >> configure.ac: >> >> AC_PREREQ(2.59) >> >> Any thoughts? Should i be posting to the developer's list? >> > > have you tried bootsteap.sh ?? > anyway i never managed to bootstrap on OSX. > > Soon we'll have a pre-bootstrappd daily archive. > > Max > > _______________________________________________ > Callweaver-users mailing list > [email protected] > http://lists.callweaver.org/mailman/listinfo/callweaver-users > _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
