[asterisk-bugs] [JIRA] (ASTERISK-26416) pjproject-bundled: configure fails to check for all required utilities

[Corey Farrell (JIRA)]

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

Corey Farrell commented on ASTERISK-26416:
------------------------------------------

Additional comment, pjproject tarball download should recognize/respect any {{--with-externals-cache=PATH}} option given to Asterisk ./configure.  This is another thing I noticed during testing of my Dockerfile for Asterisk testsuite that pjproject was being downloaded every time.  If you'd like I can open a separate ticket for this.

> pjproject-bundled: configure fails to check for all required utilities
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-26416
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26416
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip/Bundling
>    Affects Versions: 13.11.2, 14.0.1, GIT
>            Reporter: Corey Farrell
>            Assignee: George Joseph
>            Severity: Minor
>
> This issue was found while working on a Centos 7 Dockerfile to run the testsuite.  When I attempted to enable bundled pjproject first it failed due to 'lack of download program'.  This was actually lack of 'which' utility.  Additional utilities that are run by pjproject bundling Makefile:
> * bzip2 (for tar extraction)
> * autoconf
> The main configure.ac should be determining if build requirements are available and fail when bundled pjproject is requested but impossible.  For finding the download program we should use AC_PROG_PATH instead of which.  We should check for / fail if otherwise unneeded utilities are missing (bzip2, autoconf).
> Additionally we should not be running utilities directly by name in third-party/pjproject/Makefile.  For example instead of {{sed}} we should run {{$\{SED\}}}.  Always use the results of ./configure!



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