From package automake18, aclocal18 and automake18 try to run 'autom4te' when they should actually run 'autom4te259' More explicitly, in /usr/local/bin/aclocal18, my $traces = ($ENV{AUTOM4TE} || 'autom4te'); should read my $traces = ($ENV{AUTOM4TE} || 'autom4te259'); Similarly, in /usr/local/bin/automake18, my $traces = ($ENV{AUTOCONF} || 'autoconf') . " "; should read my $traces = ($ENV{AUTOCONF} || 'autoconf259') . " "; I made those changes post-installation and now aclocal18/automake18 work fine. Fix: See above (although I've not investigated the best way to fix this within the port; I just patched aclocal18/automake18 post-installation to make them work) How-To-Repeat: I cvsup'd my ports collection before building. I did have an old version of autom4te lying around when I built package automake18 (which in turn pulled in autoconf259) $ pkg_info -W /usr/local/bin/autom4te /usr/local/bin/autom4te was installed by package autoconf-2.53_1 Maybe the existence of that file confused things. But since automake18 explicitly pulls in autoconf259, then I think it should refer to autom4te259 Without the fix, the wrong (old) version of autom4te is run, which gives a number of strange and confusing errors.
Responsible Changed From-To: freebsd-ports-bugs->ade Over to maintainer.
State Changed From-To: open->closed Modified a couple of existing patches to also ensure reference to version 2.59 of autoconf. Thanks for the heads-up.