編譯opus lib失敗 error AM_PROG_LIBTOOL

從官網下載了最新的opus 1.3的代碼,然后按照readme說明進行編譯。

配置的時候出現(xiàn)如下錯誤:

$ ./autogen.sh

Updating build configuration files, please wait....

configure.ac:38: warning: macro 'AM_PROG_LIBTOOL' not found in library

configure.ac:38: error: possibly undefined macro: AM_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


搜索了一下,缺少libtool,安裝解決

$ sudo apt-get install libtool



接著來了第二個錯誤:

$ ./autogen.sh

Updating build configuration files, please wait....

libtoolize: putting auxiliary files in '.'.

libtoolize:? error: linking '/usr/share/libtool/build-aux/ltmain.sh' to './' failed

libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.

libtoolize:? error: linking '/usr/share/aclocal/libtool.m4' to 'm4/' failed

libtoolize:? error: linking '/usr/share/aclocal/ltoptions.m4' to 'm4/' failed

libtoolize:? error: linking '/usr/share/aclocal/ltsugar.m4' to 'm4/' failed

libtoolize:? error: linking '/usr/share/aclocal/ltversion.m4' to 'm4/' failed

libtoolize:? error: linking '/usr/share/aclocal/lt~obsolete.m4' to 'm4/' failed

autoreconf: libtoolize failed with exit status: 1

原因是opus編譯代碼在我的共享文件夾下面,造成了權限問題。對我用的虛擬機VBox。

重新克隆一份opus代碼到/usr/home下,再次執(zhí)行autogen.sh,成功。



there's actually another situation that can cause the libtoolize that was not really addressed here. Permission and access issues. Consider the following situation: you're in virtualbox and trying to run libtoolize out of a VBox Shared folder, you will get this error. Move the project within the machine, error is gone.

ref:?https://stackoverflow.com/questions/31939729/regenerate-makefiles-sh-generates-libtoolize-linking-error-when-compiling-irstlm?

最后編輯于
?著作權歸作者所有,轉載或內容合作請聯(lián)系作者
【社區(qū)內容提示】社區(qū)部分內容疑似由AI輔助生成,瀏覽時請結合常識與多方信息審慎甄別。
平臺聲明:文章內容(如有圖片或視頻亦包括在內)由作者上傳并發(fā)布,文章內容僅代表作者本人觀點,簡書系信息發(fā)布平臺,僅提供信息存儲服務。

相關閱讀更多精彩內容

友情鏈接更多精彩內容