Grp_lock Error When Compiling Against Pjproject

Home » Asterisk Users » Grp_lock Error When Compiling Against Pjproject
Asterisk Users 3 Comments

Hello Asterisk,

Would someone be kind enough as to add the issue:

grp_lock error when compiling against pjproject

and solution:

delete the rogue install in /usr/local/include

To the WIKI page about installing pjsip.

I tried to update the WIKI but don’t seem to have a way to do it.

I know it’s not supposed to happen and I know what I did wrong, but it’s hard to imagine I’ll be the last person to make that mistake.

Thanks, Ira

3 thoughts on - Grp_lock Error When Compiling Against Pjproject

  • I’m including the asterisk-users mailing list on this reply, as there’s no reason to take this discussion off list.

    I’m not sure what bug list you’re referring to. However, the page on the wiki that documents common errors and their appropriate correction [1]
    attempts to provide the exact error message that users will see when they encounter that situation. I’d be happy to update it with whatever error you ran into, but to do so we need to know the exact messages. Alluding to error messages without providing them usually leads to more confusion, not less.

    [1]
    https://wiki.asterisk.org/wiki/display/AST/Installing+pjproject#Installingpjproject-IssuesandWorkarounds

    Matt

  • I ran into the same problem a few weeks ago. The error is during the asterisk-12 build and it’s related to using a version of pjproject from before file made a grp_lock commit in pjproject in September.

    res_pjsip/pjsip_distributor.c: In function ‘find_dialog’:
    res_pjsip/pjsip_distributor.c:139:25: error: ‘pjsip_transaction’ has no member named ‘grp_lock’
    pj_grp_lock_release(tsx->grp_lock);
    ^
    make[1]: *** [res_pjsip/pjsip_distributor.o] Error 1

    The fix is to clean out all old copies pf pjproject and re-clone from github.