Bug 36766
| Summary: | Incompatibility between autoconf, automake and libtool | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | lev <lev> |
| Component: | Individual Port(s) | Assignee: | Ade Lovett <ade> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-ports->portmgr Over to portmgr territory Responsible Changed From-To: portmgr->ade I'll be looking at all things libtool prior to 4.8-RELEASE State Changed From-To: open->analyzed Specific inter-version dependencies between libtool, autoconf, and automake will be dealt with after true versioning support has been added to the autoconf/automake ports. State Changed From-To: analyzed->closed As far as I am aware, this is now fixed with the new bsd.autotools.mk |
When devel/libtool port are installed, it put aclocal-related files to `${PREFIX}/share/aclocal/libtool.m4'. But it is directory for automake-1.5 port. And autoconf-2.53 & automake-1.5 ports IS NOT COMPATIBLE with libtool-1.3.6: %cat configure.in AC_INIT(src/test.c) AM_INIT_AUTOMAKE([test], [0.1]) AC_PROG_CC AC_PROG_LIBTOOL AM_CONFIG_HEADER(config.h) AC_OUTPUT([Makefile src/Makefile]) % %cat Makefile.am SUBDIRS = src % %libtoolize -f -c && aclocal && autoheader && automake -ac && autoconf configure.in:6: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:8: warning: do not use m4_regexp: use regexp or m4_bregexp % %./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets ${MAKE}... yes checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc checking build system type... i386-unknown-freebsdelf4.4 checking host system type... i386-unknown-freebsdelf4.4 checking for ranlib... ranlib checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes loading cache /dev/null within ltconfig ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed % When I try to use OLD automake, aclocal and autoconf it COULD NOT find libtool.m4 and AC_PROG_LIBTOOL, because libtool.m4 is in `${PREFIX}/share/aclocal/libtool.m4', not in `${PREFIX}/share/automake14/aclocal/libtool.m4': %libtoolize -f -c && aclocal14 && autoheader213 && automake14 -a -c && autoconf213 %libtoolize -f -c && aclocal14 && autoheader213 && automake14 -a -c && autoconf213 You should update your `aclocal.m4' by running aclocal. autoconf: Undefined macros: configure.in:4:AC_PROG_LIBTOOL % This situation could be fixed by copying ${PREFIX}/share/automake14/aclocal/* into ${PREFIX}/share/automake14/aclocal/, but it is not good solution, IMHO.