> > > What exactly do you dislike in avifile auto* stuff? > > > > For one point its horrible broken. > In most cases users have totally broken enviroments.
I had automake/autoconf/libtool from RH 7.0 and I never had problems with it. Only when trying to compile avifile from CVS, the configure script complained about a broken "ls" command, which is definitively not case. I solved the problem by upgrading automake/autoconf/libtool to their newest versions. After upgrading, several autoconf scripts from other packages didn't work anymore, so I had to upgrade their configure.in's. I think, this is mainly a problem of the GNU development tool themselves, because the current autoconf breaks even "famous" packages like gtk, and they don't seem to have a backward compatibility mode. I hoped, that with the release of gcc-3, the life of developers would become more easy, because nobody really needs to use the 2.9* (worst: 2.96) versions anymore. But now it seems, that this mess with version conflicts was just moved to the other GNU development tools.... _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
