Summary: | ASTERISK-08116: still AC_PROG_LD issues... | ||
Reporter: | Luigi Rizzo (rizzo) | Labels: | |
Date Opened: | 2006-11-12 14:12:01.000-0600 | Date Closed: | 2006-11-12 23:51:40.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/Configuration |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | on a system without libtool installed i get the output below. Still some missing piece if we want AC_PROG_LD... russel, can you have a look at this ? > ./bootstrap.sh Generating the configure script ... configure.ac:134: warning: AC_PROG_SED is m4_require'd but is not m4_defun'd configure.ac:134: AC_PROG_SED is required by... acinclude.m4:653: AST_PROG_LD is expanded from... configure.ac:134: the top level configure:3781: error: possibly undefined macro: AC_PROG_SED If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:134: warning: AC_PROG_SED is m4_require'd but is not m4_defun'd configure.ac:134: AC_PROG_SED is required by... acinclude.m4:653: AST_PROG_LD is expanded from... configure.ac:134: the top level | ||
Comments: | By: Russell Bryant (russell) 2006-11-12 23:51:39.000-0600 I suspect the issue here is that the AC_PROG_SED macro is included in autoconf 2.60, but not in 2.59. So, I have copied the macro into our acinclude.m4 file so that 2.59 will still work. This was done in the 1.4 branch and the trunk in revisions 47527 and 47529. |