[asterisk-bugs] [JIRA] (ASTERISK-28623) pjsip: PJPROJECT_CONFIGURE_OPTS install location not honored

George Joseph (JIRA) noreply at issues.asterisk.org
Mon Dec 2 09:34:32 CST 2019


     [ https://issues.asterisk.org/jira/browse/ASTERISK-28623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Joseph updated ASTERISK-28623:
-------------------------------------

    Assignee: Richard Frith-Macdonald
      Status: Waiting for Feedback  (was: Triage)

The bundled version of pjproject doesn't actually install anything to that location.  In fact, it doesn't install anything at all.  The bundled version is compiled but then linked into libasteriskpj.so which gets installed into whatever prefix you've specified with asterisk's ./configure.

We added /opt/pjproject to the pjproject configure only as a failsafe so that if something got messed up with the install, it wouldn't overwrite anything in the system directories.

Are you seeing something different?  If so, logs or error messages would be appreciated

> pjsip: PJPROJECT_CONFIGURE_OPTS install location not honored
> ------------------------------------------------------------
>
>                 Key: ASTERISK-28623
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28623
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Third-Party/pjproject
>    Affects Versions: 17.0.0
>            Reporter: Richard Frith-Macdonald
>            Assignee: Richard Frith-Macdonald
>            Severity: Minor
>
> This appears to be deliberate (judging by the comment in third-party/pjproject/Makefile.rules), but its not clear to me why this was done.
> The --prefix= option is explicitly overridden in Makefile.rules to set the install location to be /opt/pjproject 
> Doing this prevents building and installing asterisk into a sandbox area (and means you need to build as root, which is generally a bad idea).
> The simple fix is to remove that override in Makefile.rules
> If there's a good reason to have that override, I suggest adding a top-level configure option to be used to override the override :-)



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



More information about the asterisk-bugs mailing list