On Tue, 7 Aug 2001, Alexander Mai gibbered:
> autoconf 2.50 in turn breaks the vast
> majority of all configure.in setups of various packages on my harddisk.
It breaks maybe twenty on my system (out of >300). Not `the vast
majority' by any means.
I'm wondering how you can have managed such an unlucky selection :)
> Also it's clear that I can neither debug all configure.in's nor
> autoconf itself - that's not an option.
Build autoconf-2.13 or 2.50 and rename the programs to autoconf-2.13 and
autoheader-2.13, then run them when needed and set AUTOHEADER and
AUTOCONF to the right binaries when running such a project's makefile.
> So what's left? libtool people insist on going ahead, I think 1.4 even
> could be built using autoconf 2.13, CVS version no longer does so.
> I don't like the idea of having two sets of auto* installed on my
> systems just to work on LessTif.
Why not? They're not very large.
--
`It's all about bossing computers around. Users have to say "please".
Programmers get to say "do what I want NOW or the hard disk gets it".'
-- Richard Heathfield on the nature of programming
