安装了libtool但找不到libtoolize [英] installed libtool but libtoolize not found

问题描述

im试图从我的Mac上的源代码构建libxml2.

im trying to build libxml2 from source on my mac.

所以我使用Mac端口安装了autoconf libtool和automake

so i have autoconf libtool and automake installed using mac ports

autoconf和automake似乎按预期工作正常.

autoconf and automake seem to be working fine as expected.

我尝试先运行autogen.sh.

i try running autogen.sh first.

libtoolize --version不幸给出

libtoolize --version unfortunately gives

-bash: libtoolize: command not found

我再次尝试跑步

sudo port install libtool

--->  Cleaning libtool
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

我尝试

locate libtool

它似乎安装得很好

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/libtool
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/man/man1/libtool.1
/Applications/Xcode.app/Contents/Developer/usr/bin/libtool
/Applications/Xcode.app/Contents/Developer/usr/share/man/man1/libtool.1
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/cross/mipsel-linux-binutils/files/110-uclibc-libtool-conf.patch
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libtool
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libtool/Portfile
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libtool/files
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libtool/files/ltmain.m4sh-allow-clang-stdlib.diff
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libtool-devel
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/libtool-devel/Portfile
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/openslp/files/libtool-tags.patch
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/devel/t1lib/files/patch-libtool-tag.diff
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/print/pdflib/files/patch-libtool.diff
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/security/steghide/files/libtool-tag.diff
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/www/apache2/files/libtool-tag.diff
/usr/bin/libtool
/usr/lib/php/build/libtool.m4
/usr/share/apr-1/build-1/libtool
/usr/share/man/man1/libtool.1

我如何使libtoolize工作?

how do i get libtoolize to work?

推荐答案

您通常需要使用glibtool和glibtoolize，因为libtool作为创建Mach-O动态库的二进制工具已经在OS X上存在. .因此，尽管端口本身仍被命名为"libtool"，但这就是MacPorts使用程序名称转换安装它的方式.

You typically need to use glibtool and glibtoolize, since libtool already exists on OS X as a binary tool for creating Mach-O dynamic libraries. So, that's how MacPorts installs it, using a program name transform, though the port itself is still named 'libtool'.

某些autogen.sh脚本(或等效脚本)将使用LIBTOOL/LIBTOOLIZE环境变量.我自己的autogen.sh脚本中有一行:

Some autogen.sh scripts (or their equivalent) will honor the LIBTOOL / LIBTOOLIZE environment variables. I have a line in my own autogen.sh scripts:

case `uname` in Darwin*) glibtoolize --copy ;;
  *) libtoolize --copy ;; esac

您可能会想要--copy标志.

注意:如果您已经使用MacPorts安装了自动工具，则带有Makefile.am文件的正确编写的configure.ac应该只需要autoreconf -fvi.如预期的那样，它应调用glibtoolize等.否则，某些软件包将分发autogen.sh或类似脚本.

Note: If you've installed the autotools using MacPorts, a correctly written configure.ac with Makefile.am files should only require autoreconf -fvi. It should call glibtoolize, etc., as expected. Otherwise, some packages will distribute an autogen.sh or similar script.

这篇关于安装了libtool但找不到libtoolize的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！