| Summary: | [patch] bsd.autotools.mk: aclocal can't find libtool macros | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Dmitry Frolov <frolov> | ||||
| Component: | Individual Port(s) | Assignee: | Ade Lovett <ade> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Responsible Changed From-To: freebsd-ports-bugs->ade This one is mine. State Changed From-To: open->feedback This will be dealt with as part of the next set of major changes to the autotools infrastructure, involving wrapper scripts around the components of autoconf/automake to more seemlessly handle multiple versions of autotools both for building ports, and for cross-development outside of the ports tree. State Changed From-To: feedback->analyzed Put into a more appropriate state, given the current under-test reworking of autoconf/automake. State Changed From-To: analyzed->feedback The latest round of updates to autotools should have fixed this. Unless I hear otherwise, I'll be closing this PR 2 weeks from today (11th August 2007). State Changed From-To: feedback->closed Submitter email address is hard-bouncing. |
aclocal from devel/automake19 fails to find libtool macros if both aclocal and libtool used in port's Makefile. That's because aclocal searches for macros (according to bsd.autotools.mk) in ${LOCALBASE}/share/aclocal${AUTOMAKE_VERSION} dir but devel/libtool* ports install their aclocal macros into ${LOCALBASE}/share/aclocal dir. Fix: One of the possible fixes (patch against bsd.autotools.mk rev 1.23): How-To-Repeat: frol@nerve ttypa:~/ports/sysutils/ipmitool$grep AUTO Makefile USE_AUTOTOOLS= autoconf:259 libtool:15 aclocal:19 automake:19 frol@nerve ttypa:~/ports/sysutils/ipmitool$make configure ===> Vulnerability check disabled, database not found ===> Extracting for ipmitool-1.8.6_1 [...] ===> Configuring for ipmitool-1.8.6_1 aclocal:configure.in:38: warning: macro `AM_PROG_LIBTOOL' not found in library configure.in:38: error: possibly undefined macro: AM_PROG_LIBTOOL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. *** Error code 1