[asterisk-bugs] [JIRA] (ASTERISK-27997) pjproject_bundled: Fix for Solaris builds. Do not undef s_addr.

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Jul 30 07:41:54 CDT 2018


    [ https://issues.asterisk.org/jira/browse/ASTERISK-27997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244326#comment-244326 ] 

Asterisk Team commented on ASTERISK-27997:
------------------------------------------

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].

> pjproject_bundled: Fix for Solaris builds. Do not undef s_addr.
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-27997
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27997
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.22.0, 15.5.0
>         Environment: Solaris 11.3
>            Reporter: Alexander Traud
>
> ASTERISK-20366 go re-introduced with the bundled PJProject. The authors of PJProject undef s_addr because of some issue in Microsoft Windows. However in Oracle Solaris, s_addr is not a structure member, but defined to map to the real structure member.
> The attached patch here, changes the only {{struct pj_in_addr}} usage to its alias {{pj_in_addr}} within Asterisk itself. For PJProject, the first patch attached to ASTERISK-20366 is re-used exactly like it was. The second patch there, is still included in Asterisk; not need to re-add it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list