On Mar 15, 2006, at 01:51 , Dag-Erling Smørgrav wrote:
libtool.m4, actually. devel/gnu-libtool installs it:
So? devel/gnu-libtool was not touched by this change, nor, indeed, were any of the devel/gnu-* autotools.
Compare and contrast what happens with the old gnu-libtool installed:
Again, devel/gnu-libtool was *not* changed.
The great majority of ports don't use aclocal, because the tarballs ship with pre-generated aclocal and configure scripts. If you didn't already know and understand that, you have no business messing with the autotool ports.
Not to put too fine a point on it, but I have forgotten more about how libtool/autoconf/automake interact than most people will ever know.
This is not a religious argument. It's a very simple technical argument: the GNU autotools used to work, now they don't.
Given that devel/gnu-{libtool,autoconf,automake} haven't been changed, I fail to understand what the problem is here. Of course, if you're mixing and matching the gnu- prefixed tools with the ports tools, then things are very likely to break. There's a big banner comment in bsd.autotools.mk, and the gnu-* ports, about that. Caveat emptor.
-aDe _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
