installed libtool but libtoolize not found

Question

i'm trying to build libxml2 from source on my mac.

so i have autoconf, libtool, and automake installed using macports

autoconf and automake seem to be working fine as expected.

i try running autogen.sh first.

libtoolize --version unfortunately gives

-bash: libtoolize: command not found 

i try running (again)

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

i try

locate libtool 

and it seems to be installed fine

/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 

how do i get libtoolize to work?

Answer 1

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'.

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 

You may or may not want the --copy flag.

---

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.

Answer 2

I hope my answer is not too naive. I am a noob to OSX.

brew install libtool solved a similar issue for me.