Bug 98435

Summary:	aclocal does not see 3rd party m4 files (e.g. the libtool one)
Product:	Ports & Packages	Reporter:	Alexander Leidinger <netchild>
Component:	Individual Port(s)	Assignee:	Ade Lovett <ade>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	ade
Priority:	Normal
Version:	Latest
Hardware:	Any
OS:	Any

Description Alexander Leidinger freebsd_committer

2006-06-03 13:10:15 UTC

When calling aclocal19 it can't find the definition for AC_PROG_LIBTOOL.
aclocal19 only searches in /usr/local/share/aclocal19, but not in
/usr/local/share/aclocal/ where libtool.m4 contains this definition.

Fix: 

As a workaround for the moment I did a
  echo /usr/local/share/aclocal > /usr/local/share/aclocal19/dirlist

aclocal knows about this dirlist file and parses the directories in there
too. So a fix woul be to add such a file with the right content to the port.

Comment 1 Alexander Leidinger freebsd_committer

2006-06-03 14:31:31 UTC

Responsible Changed
From-To: freebsd-ports-bugs->ade

Assign to maintainer.

Comment 2 Ade Lovett freebsd_committer

2006-08-22 04:39:12 UTC

State Changed
From-To: open->analyzed

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.

Comment 3 Ade Lovett freebsd_committer

2007-07-28 07:38:25 UTC

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

Comment 4 Ade Lovett freebsd_committer

2007-08-11 23:43:14 UTC

State Changed
From-To: feedback->closed

As promised, close on a 2-week timeout working on the basis that 
recent major updates to the autotools systems have now resolved the problem.