On Jul 8, 2007, at 12:06 PM, Martin Joseph wrote:

>>>
>>> On Jun 22, 2007, at 1:39 AM, Jason Ketterman wrote:
>>>
>>>> On Jun 22, 2007, at 3:10 AM, Martin Joseph wrote:
>>>
>>>> Thanks for the pointers and the help, unfortunately,  that didn't
>>>> fix
>>>> my problem.
>>>>
>>>> Any other ideas?
>>>> Marty
>>>>
>>>
>>> I also have compiled many bootstrapped versions of the callweaver
>>> code
>>> over the last two months, and have had no problem with those.  
>>> However
>>> I too am having the same problem with the rc4 build.
>>
>> Has anyone out there built the RC4 release on OSX successfully?<snip?

I received the following email off list today:

> I saw your message at http://www.mail-archive.com/callweaver- 
> [EMAIL PROTECTED]/msg00396.html, and I think I have the  
> solution. I made 2 small changes to the source code. Here are the  
> diffs for original vs. modified.
>
> % diff callweaver-1.2.0_rc4/funcs/func_strings.c ../ 
> callweaver-1.2.0_rc4/funcs/func_strings.c
> 121c121
> <               opbx_LOG(LOG_ERROR, "Syntax: %s\n",  
> fieldqty_func_syntax);
> ---
> >               opbx_log(LOG_ERROR, "Syntax: %s\n",  
> fieldqty_func_syntax);
>
>
> % diff callweaver-1.2.0_rc4/corelib/pbx.c ../callweaver-1.2.0_rc4/ 
> corelib/pbx.c
> 7003c7003
> < static int pbx_checkcondition(char *condition)
> ---
> > int pbx_checkcondition(char *condition)
>
>
> After that, I was able to build successfully and then run the  
> daemon and console.
>
> I don't see a way to follow up to the mailing list thread since I  
> have only just subscribed, so I'd appreciate it if you post back to  
> the thread if this works for you.
>
> BTW, I'm on Intel Mac 10.4.10. Good luck.
>
> Darin Franklin
I did the changes Darin describes and RC4 built for me on OSX 10.4.9.

Hope this helps someone else...  I see that trunk has moved beyond  
this and has other issues it seems...

Marty


_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users

Reply via email to