Asterisk 18.10.0 fails to compile with res_pjsip/pjsip_message_filter.c:234:9: error: unknown type name ‘pjsip_sdp_info’; did you mean ‘pjsip_regc_info’? Attaching build log and emerge --info in a bit Reproducible: Always
Created attachment 765459 [details] build log
Created attachment 765460 [details] emerge --info output
Confirmed. Best guess at least net-libs/pjproject-2.12 is needed. https://github.com/pjsip/pjproject/commit/69a89a26dd6981ba81ae93beaaece9cdbfd24290
I believe asterisk still ships with pjproject-2.10, so 2.12 being a requirement is a little unlikely. This is a wild guess but maybe this commit has something to do with it? https://github.com/asterisk/asterisk/commit/b59bd3d3e47b7d8d2924d5566b2d8cbe9f9464f2 Perhaps before this commit bundled pjproject had always been used despite net-libs/pjproject being pulled in as a dependency?
(In reply to and from comment #3) > Confirmed. > Best guess at least net-libs/pjproject-2.12 is needed. > > https://github.com/pjsip/pjproject/commit/ > 69a89a26dd6981ba81ae93beaaece9cdbfd24290 net-libs/pjproject-2.12 helps
If true, it might be unintended. Asterisk seems to still bundle 2.10 with version 18.10: See: https://github.com/asterisk/asterisk/tree/18.10/third-party/pjproject
I see now what's happening. This patch is needed, I added it as a user patch in /etc/portage and asterisk now compiles fine: https://raw.githubusercontent.com/asterisk/asterisk/7728210352944d323a4189deba31c67105adcefd/third-party/pjproject/patches/0130-sip_inv-Additional-multipart-support-2919-2920.patch This was added to the 18.10 branch with this commit: https://github.com/asterisk/asterisk/commit/0d53ce35f9f1ef83c5157e75866fce79d9e2bae5
Clarification: the patch quoted above is meant to be applied against net-libs/pjproject-2.10-r2:0/2.10, not net-misc/asterisk-18.10.0:0/18
*** Bug 834356 has been marked as a duplicate of this bug. ***
So, maybe another solution would be to add net-libs/pjproject-2.12 to portage? However, not all of the patch files will apply properly. The "enable-ssl" patch being one of them. @George, would you mind opening a new bug report for net-libs/pjproject with your proposed patch for 2.10? It works for me. Eventually, 2.12 might make it into portage too. Thanks
I've created https://bugs.gentoo.org/834491 for anyone who's interested in monitoring this.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=74bc4476b50218718af7c43038176f1d69c50e61 commit 74bc4476b50218718af7c43038176f1d69c50e61 Author: Jaco Kroon <jaco@uls.co.za> AuthorDate: 2021-07-24 08:36:57 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-06-15 13:32:11 +0000 net-libs/pjproject: Version 2.12.1. Upstream release. Remove the need for custom patches (which is still required but no longer applies, instead, rely on ./configure detecting openssl, we do depend on it, and only --disable-ssl works, passing --enable-ssl also effectively disables ssl). Compile tested asterisk 13, 16 and 18 (in-tree versions) against this. Would appreciate a double-check on this one. One version from each is sufficient. Since the two libraries that were the target of parallel build failures are now one, I believe the parallel build issue is fixed too. Included patch for CVE-2022-31031 Closes: https://bugs.gentoo.org/833765 Closes: https://bugs.gentoo.org/817803 Closes: https://bugs.gentoo.org/808099 Closes: https://bugs.gentoo.org/834491 Bug: https://bugs.gentoo.org/803614 Bug: https://bugs.gentoo.org/765799 Bug: https://bugs.gentoo.org/829894 Package-Manager: Portage-3.0.20, Repoman-3.0.2 Signed-off-by: Jaco Kroon <jaco@uls.co.za> Closes: https://github.com/gentoo/gentoo/pull/21761 Signed-off-by: Joonas Niilola <juippis@gentoo.org> net-libs/pjproject/Manifest | 1 + .../files/pjproject-2.12.1-CVE-2022-31031.patch | 41 +++++++ net-libs/pjproject/pjproject-2.12.1.ebuild | 125 +++++++++++++++++++++ 3 files changed, 167 insertions(+)
