[
https://issues.apache.org/jira/browse/TS-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Peach resolved TS-1852.
-----------------------------
Resolution: Fixed
Sure.
> centos5.9 autoreconf -i failed
> --------------------------------
>
> Key: TS-1852
> URL: https://issues.apache.org/jira/browse/TS-1852
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Reporter: helaku
> Assignee: James Peach
> Fix For: 3.3.3
>
>
> {code}
> [root@admin trafficserver]# autoreconf -i
> configure.ac:987: warning: AC_PROG_SED is m4_require'd but is not m4_defun'd
> configure.ac:987: AC_PROG_SED is required by...
> build/ax_path_generic.m4:164: AX_PATH_GENERIC is expanded from...
> build/ax_lib_curl.m4:38: AX_LIB_CURL is expanded from...
> configure.ac:987: the top level
> configure.ac:987: warning: AC_PROG_SED is m4_require'd but is not m4_defun'd
> configure.ac:987: AC_PROG_SED is required by...
> build/ax_path_generic.m4:164: AX_PATH_GENERIC is expanded from...
> build/ax_lib_curl.m4:38: AX_LIB_CURL is expanded from...
> configure.ac:987: the top level
> Putting files in AC_CONFIG_AUX_DIR, `build/aux'.
> configure.ac:987: warning: AC_PROG_SED is m4_require'd but is not m4_defun'd
> configure.ac:987: AC_PROG_SED is required by...
> build/ax_path_generic.m4:164: AX_PATH_GENERIC is expanded from...
> build/ax_lib_curl.m4:38: AX_LIB_CURL is expanded from...
> configure.ac:987: the top level
> configure.ac:987: warning: AC_PROG_SED is m4_require'd but is not m4_defun'd
> configure.ac:987: AC_PROG_SED is required by...
> build/ax_path_generic.m4:164: AX_PATH_GENERIC is expanded from...
> build/ax_lib_curl.m4:38: AX_LIB_CURL is expanded from...
> configure.ac:987: the top level
> configure.ac:580: error: possibly undefined macro: AC_PROG_SED
> If this token and others are legitimate, please use m4_pattern_allow.
> See the Autoconf documentation.
> autoreconf: /usr/bin/autoconf failed with exit status: 1
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
