[asterisk-bugs] [JIRA] (ASTERISK-16951) [patch] configure.ac in 1.4.37 broken with autoconf 2.60

[Kevin Harwell (JIRA)]

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

Kevin Harwell updated ASTERISK-16951:
-------------------------------------

    Target Release Version/s: 16.3.0

> [patch] configure.ac in 1.4.37 broken with autoconf 2.60
> --------------------------------------------------------
>
>                 Key: ASTERISK-16951
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-16951
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/BuildSystem
>    Affects Versions: 13.19.0, 15.2.0
>            Reporter: Stéphan Kochen
>            Assignee: Alexander Traud
>            Severity: Minor
>              Labels: patch
>      Target Release: 13.20.0, 15.3.0, 16.0.0, 16.3.0
>
>         Attachments: compute_int.patch
>
>
> It looks like with revision 290177, because of AC_COMPUTE_INT, the autoconf requirement was silently bumped to at least 2.60a. But AC_PREREQ doesn't reflect this.
> Generating a configure script with 2.60 produces syntax errors such as:
> ./configure: line 20765: syntax error near unexpected token `ac_cv_sizeof_fd_set_fds_bits,'
> ./configure: line 20765: `AC_COMPUTE_INT(ac_cv_sizeof_fd_set_fds_bits, sizeof(foo.fds_bits[[0]]), $ac_includes_default'
> error: Bad exit status from /var/tmp/rpm-tmp.1037 (%build)
> (The macro simply isn't expanded, because it doesn't exist.)
> ****** ADDITIONAL INFORMATION ******
> I've tested and successfully built with autoconf 2.60b, but mind that both 2.60a and 2.60b are old and officially unstable releases.



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