Autoconf automake & libtool on MacOS X
April 8th, 2006
I have just finished my first autotools project on the MacOS. Until today I deployed software only in Python or Java. I already worked on C and C++ projects that used libtool and automake and autoconf, but I had not to write the configure scripts myself or I developed them on GNU/Linux.
In fact I’m afraid most of the problems I encountered was MacOS X fault + my ignorance. That is to say libtoolize does not exist: it is called glibtoolize. So if I do not rename it, autoreconf simply does not work.
Probably I just had to set the LIBTOOLIZE environment variable to glibtoolize. However my solution works. The error I got was
Can't exec "libtoolize": No such file or directory at /opt/local/share/autoconf/Autom4te/FileUtils.pm line 288, <GEN3> line 3.
autoreconf: failed to run libtoolize: No such file or directory
Well… I’ve to fine tune it. I go.
2 Responses to “Autoconf automake & libtool on MacOS X”
1Vijay
December 9th, 2006 @ 11:02
I created a soft link from /opt/local/bin/libtoolize –> glibtoolize, which fixed that error in my liboil compilations.
2Enrico Franchi
December 9th, 2006 @ 15:10
Yes, I suppose it works. I suppose the best thing to do is to use the LIBTOOLIZE env variable (IIRC). That should be a rather clean way to do the deed.
Moreover I found out that many autotools problems came from using autotools from darwin ports while macos x libtool infos are in /usr/share. I fixed it again with some simlinks.
Leave a Reply