Summary:	ASTERISK-28202: pjproject: fails to build on ppc64el
Reporter:	Timothy Pearson (tpearson-raptor)	Labels:	pjsip
Date Opened:	2018-12-08 19:17:27.000-0600	Date Closed:
Priority:	Minor	Regression?	No
Status:	Open/New	Components:	Third-Party/pjproject
Versions:	16.0.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	IBM Linux on POWER server, Debian Stretch	Attachments:
Description:	The embedded pjproject source needs the obsolete config.guess file updated to properly detect the ppc64el platform.  Copying in a newer version of config.guess allows Asterisk to build with the embedded pjproject sources.
Comments:	By: Asterisk Team (asteriskteam) 2018-12-08 19:17:29.653-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2018-12-10 08:30:03.862-0600 Will you be providing a patch on Gerrit which updates this? We can forward it on to PJSIP afterwards. By: Timothy Pearson (tpearson-raptor) 2018-12-10 16:43:27.651-0600 I'm not sure a patch is the right way to go; the newer config.guess file should literally be copied from the main Asterisk source over the obsolete PJSIP config.guess file.  A difference between the two files will be very large and not all that useful from what I can see? By: Joshua C. Colp (jcolp) 2018-12-10 17:13:57.236-0600 We don't include the source code of PJSIP in Asterisk. It is downloaded and then patches applied (to fix problems not yet in a release, or for build purposes). Either the build system has to be updated to do this copying, or a patch file created that is applied to the downloaded and extracted source code. By: Timothy Pearson (tpearson-raptor) 2018-12-10 17:32:55.152-0600 For now the safest / cleanest solution would definitely be an update to the build system.  All it would take is upstream patching something, even whitespace, out of the config.guess file to break a patch of the size we are talking about. I've gone ahead and reported the issue upstream in the interim as well via their mailing list.