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

[Richard Frith-Macdonald (JIRA)]

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

Richard Frith-Macdonald commented on ASTERISK-28623:
----------------------------------------------------

Sorry I never got back on this ... for some reason I never received any emails from the bug tracker.
Anyway, here's a log of the error caused by this bug:

$ make install
/bin/install: cannot create directory ‘/opt/pjproject’: Permission denied
make[2]: *** [_install] Error 1
make[1]: *** [pjproject] Error 2
make: *** [third-party-install] Error 2

This is on CentOS-7 systems ... it may well be the case that pjproject is never installed, but as you can see the installation process tries to create the directory, which means you can't build/install asterisk unless you are root,  which is real  a pain for packaging and automated testing.

> 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
>            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)