您可以在 configure.ac 文件的顶部添加以下行来包含它: m4 m4_include([libtool.m4]) 确保aclocal 工具已运行,且能够找到 libtool.m4 文件。这通常意味着 libtool 应该已正确安装在您的系统上。 确认系统是否已安装libtool及其相关开发文件: 您可以通过运行 libtool --version 来
解决“possibly undefined macro: AC_PROG_LIBTOOL” 今天特别花1688在51buy.com上买了台同方的笔记本用于mooon的开发,先是安装了Fedora,觉得不好,想安装openSuSE,但发现安装包太大,最后仍选择了ubuntu 12.04,默认没有安装automake等工具,按提示逐一进行了安装,遇到如下这个错误时,表示libtool没有安装: $ sh first_on...
解决“possibly undefined macro: AC_PROG_LIBTOOL” 今天特别花1688在51buy.com上买了台同方的笔记本用于mooon的开发,先是安装了Fedora,觉得不好,想安装openSuSE,但发现安装包太大,最后仍选择了ubuntu 12.04,默认没有安装automake等工具,按提示逐一进行了安装,遇到如下这个错误时,表示libtool没有安装: $ sh first_on...
当安装configure.ac:17: error: possibly undefined macro: AC_PROG_LIBTOOL 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 出现之后来那叫一个郁闷啊,在线搜索。该解决方案终于被,欲哭无...
configure.ac:64: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoconf ERROR 只需要执行“sudo apt-get install libtool”安装好即可解决。
error: possibly undefined macro: AC_PROG_LIBTOOL解决方案,error:possiblyundefinedmacro:AC_PROG_LIBTOOLm4
configure.ac:64: error: possibly undefined macro: AC_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoconf ERROR 只需要执行“sudo apt-get install libtool”安装好即可解决。
[root@yoshino iim-3-party]# cd protobuf-3.10.1/ [root@yoshino protobuf-3.10.1]# ./autogen.sh + mkdir -p third_party/googletest/m4 + autoreconf -f -i -Wall,no-obsolete aclocal:configure.ac:51: warning: macro `AM_SILENT_RULES' not found in...
简介: error: possibly undefined macro: AC_PROG_LIBTOOL 具体错误: configure.ac:53: error: possibly undefined macro: AC_PROG_LIBTOOL 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...
安装时出现configure.ac:17: error: possibly undefined macro: AC_PROG_LIBTOOL 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